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

Project Portal
| See Also How to: Associate a Work Item with a Test How to: Create a Bug |
| ### Next Steps Open a Bug Conduct Exploratory Testing |
| Select and Run Customer Requirement Tests ( 3 : VAL : 2 : 2.1 ) ( 3 : VAL : 2 : 2.2 ) Tester
Activity: Select and Run Customer Requirement Tests
Tester
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Tester Informed: Developer
### Overview When functionality is implemented in a build, the functionality is ready to test. The tester must configure the test environment required to run the appropriate tests against the build. Then the tests are run, and test results are captured. Test results vary from a successful run to a blocking system crash. Depending on the test results, the tester documents the results against the associated scenario or requirement. # Entry Criteria Task Work Item A test task exists to test a scenario or requirement. Test Approach Provides information to identify and prioritize tests. Build Notes Indicate if the latest build contains functionality to be tested. When: Tests are written for functionality that is available in a build. # 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 | Set Up Test Environment | Retrieve, install, and configure the test environment required to run the tests. This includes hardware, software, and test data.
3 | Get the Build | Get the build from version control and configure it in the test environment so that it is ready for testing.
4 | Run the Tests | Open the test project in Visual Studio. Use Test Manager or Test View to select the tests to be run. Run the tests. Use the test data identified by the test approach document for the current iteration.
5 | Analyze Test Results | If the tests are for a scenario, attach the test results to the scenario work item. If the tests are for a requirement, attach the test results to the requirement work item. Check the test results against expected results. Open a bug work item if the results do not meet expectations.
6 | Close the Test Task | If all the tests for the test task run unblocked, close the test task work item. Note that an unblocked test is one that runs to completion and either succeeds or fails. Notify the developer who implemented the scenario or requirement that there are no blocking issues. If all of the test tasks for a scenario or requirement are closed, close the scenario or requirement work item.
# Exit Criteria
| The test task is closed because all of the tests have run unblocked.
| Requirement is closed if all tests for requirement succeed.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |