|
|
|
|
|
|
Test a Quality of Service Requirement
Tester |
|
|
Participating Roles
Responsible:
Tester |
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.
Entry Criteria
- The quality of service requirement has been written, reviewed, and storyboarded.
Activities
|
1 |
Define Test Approach |
- Determine the project context.
- Determine the test mission.
- Assess possible testing techniques.
- Define the test metrics.
- Define the goals and test data.
|
2 |
Write Performance Tests |
- Understand the objective of the test.
- Specify the test configuration.
- Design the test.
- Document the test steps.
|
3 |
Write Security Tests |
- Explore entry points.
- Identify system flaws.
- Exploit system weaknesses.
|
4 |
Write Stress Tests |
- Design the test.
- Write the test.
|
5 |
Write Load Tests |
- Understand the objective of the load test.
- Design the test.
- Write the test.
|
6 |
Select and Run a Test Case |
- Determine which tests to run.
- Identify the test configuration.
- Get the build.
- Run the test.
- Analyze the results.
- Close the work item.
|
7 |
Open a Bug |
- Identify a bug.
- Assign the bug.
|
8 |
Conduct Exploratory Testing |
- Establish session length.
- Meet persona expectations.
- Envision new persona goals.
|
Exit Criteria
|
All of the performance, stress, security, and load tests have been run and resulting bugs have been reported. | |
|
|
|
|
© 2005, 2006 Microsoft Corporation. All rights reserved.
Version 4.0.1 |
|