background image
<< Determining What to Test | Test Inputs from Rational Rose >>
Working with Test Cases
<< Determining What to Test | Test Inputs from Rational Rose >>
Chapter 6 - Test Planning
Working with Test Cases
A test case describes the testable and verifiable behavior in a system. A test case can
also describe the extent to which you will test an area of the application. Existing
project artifacts, such as requirements, provide information about the application and
can be used as test inputs for your test cases. TestManager provides built-in test input
types, but almost any artifact can be used as a test input.
For example, here's what the following artifacts offer as test inputs:
Requirements describe a condition or capability to which a system must conform.
Visual models provide a graphic representation of a system's structure and
You can also define custom test input types, such as source code, software builds, and
functional specifications.
After you identify your test inputs, you can create test cases and associate them with
test inputs. These associations allow you to respond if test inputs change. These
changes might require you to change the test cases or their implementations.
Exercise: Create a test case for the Arrange Shipment use case.
In the right pane of TestManager, right-click the Test for Arrange Shipment UC folder,
and from the shortcut menu click Insert Test Case.
The New Test Case dialog box appears. Information you include in these boxes
helps to define the test case which will be inserted under the test case folder.
On the General tab:
In the Name box, type
Display Estimated Ship Date
In the Description box, type:
Warehouse system gets order and responds with estimated ship date.
In the Owner box, make sure that
is selected.
Click OK.
The test case Display Estimated Ship Date appears in the test plan hierarchy (see
Figure 25).