|
|
 |
 |
 |
 |
 |
Test a Scenario
 Tester
|
 |
|
Participating Roles
Responsible:
Tester |
A scenario is divided into test tasks as well as development tasks. These tasks are assigned to testers to develop and run test cases. The assignment of a scenario to test indicates that the functionality has been integrated into a build and is ready to be tested. Validating that a build reflects the functionality envisioned in the scenario requires an understanding of the scenario and its boundary conditions. Validation tests must be written to cover the complete functionality and the boundary conditions of the scenario. Validation tests are run until none are blocked. Bugs are created to report any bugs that were found.
Entry Criteria
- A test task for the scenario has been assigned outlining the area of the scenario being tested.
Dependencies:
- The scenario has been written, reviewed, and if necessary, storyboarded.
Activities
|
|
1 |
Define Test Approach |
- Determine the project context.
- Determine the test mission.
- Assess possible testing techniques.
- Define the test metrics.
|
|
2 |
Write Validation Tests |
- Identify the test area and environment.
- Identify test case flow details.
- Write the test cases.
|
|
3 |
Select and Run a Test Case |
- Determine which test to execute.
- Identify the test configuration.
- Get the build.
- Execute the test.
- Analyze the test results.
- Close the work item.
|
|
4 |
Open a Bug |
- Identify a bug.
- Assign the bug.
|
|
5 |
Conduct Exploratory Testing |
- Establish session length.
- Meet persona expectations.
- Envision new persona goals.
|
Exit Criteria
 |
All of the validation tests have been run and any resulting bugs have been reported. | |
 |
 |
 |
 |
© 2005, 2006 Microsoft Corporation. All rights reserved.
Version 4.0.1 |
 |
Overview 