Skip to main content

MSF for Agile Software Development

Go Search
Home
  
MSF for Agile Software Development > Wiki Pages > WorkDefinition - Test a Quality of Service Requirement  

WorkDefinition - Test a Quality of Service Requirement

WorkDefinition Information

Test a Quality of Service Requirement

Description

The assignment of a quality of service requirement to test indicates that the build reflects the constraint and is ready to be tested. To validate a build reflects the constraints envisioned in a quality of service requirement requires knowledge beyond the constraint. In many cases, scenarios are attached to the requirement to show the areas to be constrained. Testing a quality of service requirement demands performance, security, stress, and load tests be completed and that none are blocked. Based on the test results, bug work items are created to document the issues discovered.

Write Stress TestsConduct Exploratory TestingWrite Performance TestsOpen a BugSelect and Run a Test CaseWrite Security TestsWrite Load TestsDefine Test Approach

Attributes

GuidanceTesting Performance Requirements, Testing Tools Tasks
Entry Criteria

The quality of service requirement has been written, reviewed, and storyboarded.

Exit Criteria

All of the performance, stress, security, and load tests have been run and resulting bugs have been reported.

Inputs and Outputs

WorkProductInputOutputAllowable States
BugNew
Load Test(none)
Manual Test(none)
Persona(none)
Quality of Service RequirementActive, Resolved
ScenarioResolved
TaskActive
Test Approach(none)
Test Result(none)
Web Test(none)

Predecessors

TypeNameDependency Type
Build a ProductFinish-Start
Divide Quality of Service Requirements into TasksFinish-Start

Successors

TypeNameDependency Type
Fix a BugStart-Start
Release a ProductFinish-Start

Last modified at 12/10/2007 3:34 PM  by Administrator