Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Next Steps Open a Bug |
| Activity: Select and Run a Test Case
Tester
|  |  |  | Test a Quality of Service Requirement |  |  |  | Quality of Service Requirement Scenario Task |
|  | Participating Roles Responsible: Tester
### Overview The most important part of testing is actually running the tests over a given build. Test results vary from completely successful execution to a system crash. Once a test case is run, it is important to record the results against the scenario or quality of service requirement. # Entry Criteria Test cases for the test task are written. A build is available with the functionality to be tested. # Sub-Activities
1 | Determine Tests to Run | Based on the test task, identify and prioritize the tests to run according to the overall test plan in the test approach document. Check the build notes for the latest build to be sure that the functionality to be tested is available.
2 | Identify Test Configuration | Retrieve, install, and set up the test configuration called for in the test. This includes hardware, software, and test data.
3 | Get the Build | Obtain the build from a version control server or authorized source.
4 | Run the Test | Choose the test folder for the scenario or quality of service requirement. Select the tests to be run. Perform each step in the test if it is a manual test. Run the test if it is an automated test or there is a test script. Use the test data in the test approach document for the current iteration.
5 | Analyze Test Results | Attach the scenario or quality of service requirement to the test results. Check the test results against expected results. Open a bug if the results do not meet expectations. Update tests to reflect proper behavior of the system. If all of the tests for a scenario or quality of service requirement run unblocked, close the work item.
6 | Close the Work Item | If all the tests for a test task run unblocked, close the work item. Notify the scenarioor quality of service requirement owner there are no blocking issues. If all of the test tasks for a scenario or quality of service requirement are closed, close the work item.
# Exit Criteria
| The test task is closed because all of the tests have run unblocked. Bugs have been created to account for unexpected behavior.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |