TEST DIRECTOR PROJECT

APPLICATION The application that will be tested is the Flight Reservation application provided by Mercury Interactive with all versions of their software. The Flight Reservation application is an application that will be used by travel agents to reserve flights and purchase tickets for individuals. FEATURES The Flight Reservation application provides the following features to travel agents: Reserve Flights/Purchase Tickets Fax Flight Ticket Orders View Graph of Ticket Purchase over a time period View Report of Ticket purchase

RELEVANT APPLICATION DETAILS The application has a security mechanism. Any name can be used as the user name, but the password is mercury. Flights cannot be reserved in the past. Only future dates can be used to reserve flights The application can be launched by navigating through the Windows Start Menu to Start Menu->Programs->Quick test Professional->Sample Applications->Flight You can also launch the application directly by executing C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe The Flight application stores information in a Microsoft Access database file found in "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight32.mdb"

EXERCISE 1: PROJECT CREATION I. Create a new TestDirector project called FlightProject [A project is the start of an application testing process. Test cases, test sets and relevant defects found in the application are housed together with a project] EXERCISE 2: PROJECT ADMINISTRATION

I. Add the following users to FlightProject Login Name Amy Bob charlie Password mercury mercury mercury Full Name Amy Jacobs Bob Anton Charlie Fiona Email Address Phone Number amy@gmail.com 555-1212 bob@gmail.com 555-1313 charlie@gmail.com 555-1414

II. Create a group named Observer and add charlie to that group EXERCISE 3: ADDING ADDITIONAL DATA FIELDS I. Add the following data fields Tab Plan Test Label Environment List Contents ALL Windows 98 Windows XP Windows 2000 Version 1 Version 2 Version 3 Version 4 Required N/A Verify Y

Track Defects

Detected in Version

*Operating System: This will indicate the Operating System that we intend this test case to run on. * Detected in version: The version where the defect was found. EXERCISE 4: TEST PLANNING I. Create the following folders and tests in the Plan Test tab. Note that the tests should all be automated. Folder Order Management Test Insert New Order Delete After Insert Open Order Search for Order Update Order Login Window Tab Order Verify Toolbar Functionality Verify Defaults

GUI

Security Analysis Tools

Help File Version Login Without Password Login With Short Password Open Report Window Open Graph Window

EXERCISE 5: TEST CASE I. Update the details about the tests being created and create appropriate test steps. The table below contains each test name and the functionality that the test should be written to test. Test Insert New Order Delete After Insert Open Order Search for Order Update Order Login Window Tab Order Verify Toolbar Functionality Verify Defaults Help File Version Login Without Password Login With Short Password Open Report Window Open Graph Window Description Test that an order for the purchase of a ticket can be inserted into the system Ensure that an existing order can be deleted Check that an existing order can be opened for edit Check that you can search for an existing order within the system Open an existing order, make changes to it and ensure that the changes are saved Verify the correct tab order for items that show up on the initial Login page of the application Check that each button on the toolbar performs the appropriate functionality Ensure that the OK button is the default button on the page Check that a help file exists and it loads Version 1.0 Ensure that a message is provided when a user attempts to login without a password Ensure that a message is provided when a user attempts to login without a password that is shorter than 4 characters Ensure that the report window can be opened Ensure that the graph window can be opened

EXERCISE 6: ADDITIONAL TEST CASES I. Look for 5 more features within the Flight Reservation application that needs to be tested. Create an appropriate design steps for each of these test cases. EXERCISE 7: TEST SETS I. Create the following Test Sets in the Run Test tab using names from the table below and including the tests shown in the left hand column.

Test Set Order_Tests

GUI_Based_Tests

Security_Tests

Tests Insert New Order Delete After Insert Open Order Search for Order Update Order Open Report Window Open Graph Window Login Window Tab Order Verify Toolbar Functionality Verify Defaults Help File Version Open Report Window Open Graph Window Login Without Password Login With Short Password