background image
<< Test Design | Add Expense Test Case >>
<< Test Design | Add Expense Test Case >>

Useful data needed in a test case

10
Possible Exceptions
List of possible exceptions that can occur
during this test. This information is used
for creating recovery scenarios.
Table 1.1: Useful data needed in a test case
We have provided below in Listing 1.1, a test case that contains all
this useful information. You should note that using tools such as
Mercury Interactive's Test Director, it is easy to capture and track
this crucial information.
Test Name:
Add Expense

Purpose:
Verify that when expense records are added
they display within the application and are
added to the database

Pre-Conditon:
Application is launched, with the main page
displayed.
Note the number of expense records displayed
Step User Action
Expected Result
1
Click the Today's Date
button
Correct system date
appears in the
available textbox
2
Enter in additional
details for an expense
record
Entered details are
displayed
3
Click the save button a. Expense is
displayed in the grid
b. Totals' textbox is
update
c. Expense record is
saved to database
Post-Condition:
Close the application