TEST DIRECTOR PROJECT



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 |Password |Full Name |Email Address |Phone Number |

|Amy |mercury |Amy Jacobs |amy@ |555-1212 |

|Bob |mercury |Bob Anton |bob@ |555-1313 |

|charlie |mercury |Charlie Fiona |charlie@ |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 |Label |List Contents |Required |Verify |

|Plan Test |Environment |ALL |N/A |Y |

| | |Windows 98 | | |

| | |Windows XP | | |

| | |Windows 2000 | | |

|Track Defects |Detected in Version |Version 1 |Y |Y |

| | |Version 2 | | |

| | |Version 3 | | |

| | |Version 4 | | |

*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 |Test |

|Order Management |Insert New Order |

| |Delete After Insert |

| |Open Order |

| |Search for Order |

| |Update Order |

|GUI |Login Window Tab Order |

| |Verify Toolbar Functionality |

| |Verify Defaults |

| |Help File Version |

|Security |Login Without Password |

| |Login With Short Password |

|Analysis Tools |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 |Description |

|Insert New Order |Test that an order for the purchase of a ticket can be inserted into the system |

|Delete After Insert |Ensure that an existing order can be deleted |

|Open Order |Check that an existing order can be opened for edit |

|Search for Order |Check that you can search for an existing order within the system |

|Update Order |Open an existing order, make changes to it and ensure that the changes are saved |

|Login Window Tab Order |Verify the correct tab order for items that show up on the initial Login page of the application |

|Verify Toolbar Functionality |Check that each button on the toolbar performs the appropriate functionality |

|Verify Defaults |Ensure that the OK button is the default button on the page |

|Help File Version |Check that a help file exists and it loads Version 1.0 |

|Login Without Password |Ensure that a message is provided when a user attempts to login without a password |

|Login With Short Password |Ensure that a message is provided when a user attempts to login without a password that is |

| |shorter than 4 characters |

|Open Report Window |Ensure that the report window can be opened |

|Open Graph Window |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 |Tests |

|Order_Tests |Insert New Order |

| |Delete After Insert |

| |Open Order |

| |Search for Order |

| |Update Order |

| |Open Report Window |

| |Open Graph Window |

|GUI_Based_Tests |Login Window Tab Order |

| |Verify Toolbar Functionality |

| |Verify Defaults |

| |Help File Version |

| |Open Report Window |

| |Open Graph Window |

|Security_Tests |Login Without Password |

| |Login With Short Password |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download