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

Project Portal
| ### Next Steps Select and Run a Test |
| Activity: Write Validation Tests
Tester
|  |  |  | Test a Scenario |  |
|  | Participating Roles Responsible: Tester
### Overview Validation tests make sure the system functionality being built matches what is specified in the scenarios. Validation tests take a “black box” view of the application and concentrate on areas most important to the end users. A validation test should not be driven by the design. To write validation tests, examine the challenges that a usage scenario might pose to the application. Not all challenging details are specified in the scenarios. Validation tests check that the functionality built into the system is what is specified in the scenario lists, using a "black box" view of the system. Identifying and writing test cases for the validation tests help testers identify problems by using test actions that mimic real-world situations. # Entry Criteria The scenario has been written, reviewed, and storyboarded. A test task for the scenario is assigned outlining the area of the scenario to be tested. Dependencies: The scenario has been written, reviewed, and if necessary, storyboarded. # Sub-Activities
1 | Identify Test Area and Environment | Isolate the area where the test is scheduled to run. Iteration tests are the set of automated test cases that run after the build verification tests. These tests, however, do not have to pass in order for a build to be successful. Tests can be run as part of the iteration tests if they are automated.
2 | Identify Test Case Flow Details | Identify the test data required for the test case. Check out the test approach worksheet. Add the test data to the appropriate iteration section of the test approach worksheet. Identify all constraints for the test cases called for in the test tasks. Identify all boundary conditions for the test cases called for in the test task. Identify all boundary conditions for the test case. Determine if the test cases can be automated. Identify procedural steps for the scenario flow.
3 | Write Test Cases | Create a test folder for the scenario if one does not already exist. Write the test documentation for manual test cases. Write the automated test cases for iteration tests. Place the test cases in the test folder for the scenario. Add any that are identified as part of the iteration tests to the iteration tests folder. Save and check the tests into version control. Save and check in the test approach worksheet.
# Exit Criteria
| All of the boundary conditions and test pairings are covered by the validation tests.
| All of the functionality of the test task is covered by the validation tests.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |