<< The activity of planning tests | Test Case Folders, Iteration, Configurations >>

Test Inputs and test plans

Chapter 1 - Introducing Rational TestManager

Test Inputs

The first step in planning your testing effort is to identify the test inputs. A test input is
anything that the tests depend on or anything that needs validation. Test inputs help
you decide what you need to test. They also help you determine what tests might
need to change based on changes in the development process. This is important in
iterative development where change is a frequent, necessary part of the process.

TestManager has three built-in test input types:

Requirements in a Rational RequisitePro® project

Elements in a Rational Rose® visual model

Values in a Microsoft Excel spreadsheet

These built-in test input types give you easy access to requirements, model elements,
and values in a spreadsheet, and let you associate these inputs with other test assets
for traceability purposes. For information, see Built-In Test Input Types on page 29.

TestManager also supports custom test input types. To use a custom test input within
TestManager, write a Test Input Adapter or use an adapter provided by Rational
Software or Rational's partners. For example, to use the tasks in a Microsoft Project as
test inputs, you would write a test input adapter for Project. For more information, see
Custom Test Input Types on page 31.

Test Plans

When you have identified your test inputs, use TestManager to create a test plan. The
test plan provides an organizational structure for the other test assets in the project.

The test plan can contain a varied collection of information and addresses many
issues including:

What tests must be performed?

When must the tests be performed and be expected to pass?

Who is responsible for each test?

Where must the tests be performed? In other words, on what hardware and
software configuration must they be run?

Projects can contain multiple test plans. You may have a plan for each phase of testing.
Different groups may have their own plans. Generally, each plan should have a single
high-level testing goal (for example, test the file maintenance utility). For information,
see Creating a Test Plan on page 33.

Each test plan can contain test case folders and test cases.