MSF for Agile Software Development Visual Studio 2005 Team System logo

Activity:

Write Validation Tests

Participating Roles

Responsible:

Tester

Overview

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.

© 2006 Microsoft Corporation. All rights reserved.

Version 4.1.0