<< Associating Iterations with a Test Case | Setting Up Traceability Using Test Inputs >>

Test Impact Analysis

Creating Test Cases

Test Impact Analysis

Test impact analysis is very important to be certain that your test scripts are providing
coverage for all your test inputs.

If a test input changes, TestManager informs you of the impact of that change on your
test plan. For example, if a requirement changes in some meaningful way, you must
know which test cases in your test plans are affected so that you can update them to
reflect requirement changes. TestManager automatically identifies and marks the
affected test cases as "suspect" for you.

To perform test impact analysis, do the following:

Objective

Task

See

Set up traceability.

Associate a test input with a test
case.

Setting Up Traceability
Using Test Inputs on
page 54

Have TestManager automatically
mark test cases as suspect when a
meaningful change takes place in a
test input.

Set up automatic test case
suspicion in built-in test input
adapters and in custom adapters.

Setting Up Automatic
Test Case Suspicion on
page 55

Keep test cases and test scripts
up-to-date during the
development life cycle.

Regularly check test inputs or test
plans to see if there are any
meaningful test input or test case
changes.

Test Case Suspicion on
page 56 or the
TestManager Help -
test case suspicion;
viewing suspect links.

Evaluate all suspect links.

If a change to a test input is
meaningful and the link is not
marked as suspect, manually mark
the link as suspect.

Clear those suspect links that are
not meaningful, such as a minor
changes, to a feature that does not
need a change in the test script.

If a change to a test case is
meaningful, for example, a new
feature is added that requires a
new test script, create the new test
script, and then clear the suspect
link.

TestManager Help:
test case
suspicion:marking
suspect links.

TestManager Help:
test case
suspicion:clearing
suspect links.