<< Test Inputs and test plans | Designing and Implementing Tests >>

Test Case Folders, Iteration, Configurations

TestManager Workflow

Test Case Folders

Within a test plan, you can create test case folders to organize your test cases
hierarchically. Common organizations may reflect system architecture, major use
cases, requirements, or combinations of these. For information, see Organizing Test
Cases with Folders on page 36.

Test Cases

The test case is the test asset in TestManager that answers the question, "What am I
going to test?" You develop test cases to define the individual things that you need to
validate to ensure that the system is working the way that it is supposed to work and
is built with the quality necessary before you can ship it.

Each test case is owned by a team member. This answers the question, "Who will do
the testing?" For information, see Creating Test Cases on page 38.

Iterations

Use iterations to specify when a test case must pass. An iteration is a defined span of
time during a project. The end of an iteration is a milestone. At some point in time
during an iteration, the product has to meet a certain quality standard to reach a
milestone. The quality standard is defined by the test cases that must pass.

Iterations might be defined by several team members -- such as project managers,
product managers, and analysts -- iteratively throughout the testing process. For
information, see Specifying When to Run Tests on page 51.

Configurations

Use configurations to specify where test cases must be run -- on what hardware and
software configurations. For example, to ensure that your test case passes when it
runs on four different operating systems, you could create a configuration for each
operating system. Then you could associate those four configurations with the test
case, to create configured test cases. In order for the test case to pass, all of its configured
test cases must pass.

Configurations might be defined by several team members -- such as project
managers, product managers, and analysts -- iteratively throughout the testing
process. For information, see Defining the Configurations to Test on page 41.