President's Message

Jury Systems Design Incorporated has created this test document to accompany the detailed design document. The test document describes the order of module testing and basic module tests. It also describes the order of module integration and some integration tests. Finally, the test document will describe who is testing what, and when they are testing it.

The System Administration sub-system will be created and tested first. Within this sub-system, the airplane and booking agent modules will be built and tested before the flight module.

Next, the Booking Agent sub-system will be built and tested. The booking module will be created and tested first, followed by the query passenger and query flight modules. Finally, the issue boarding passes module will be built and tested.

Test personnel and dates are assigned as follows:

March 14-15: System Administration
- Rob Vollman
- Andrew Taylor
- Charanjeet Jugdev
- Jerry Coolidge
March 15-16: Booking Agent
- Jamie Kromrey
- Josephine Ng
- Hanna Dang
- Ernest Domshy
March 16: Interface Design
- Michael Downey
- Andrew MacNeil
March 16-18: Integration
- Alvin Schur

These dates are tentative and subject to change.

Integration Testing

The integration tester will login to the System Administration sub-system and add a the 'test' booking agent to the database. Then the test airplane types and test flights will be added.

Then the integration tester will login to the Booking Agent sub-system as 'test', the newly added booking agent. The integration tester will then add the bookings listed in the initial database values, and perform the all the tests for the Booking Agent modules.

Additional flights will be added, passengers booked on them, and boarding passes issued.

System Administrtation Sub-system Module Testing

Flights

Test add option

Case1: (all valid inputs)
- User pushes flight tab in main menu then the sub flight menu appears.
- User then selects add tab in flight sub menu and a screen appears with all the empty flight fields, except a Flight Number field which will be assigned by the computer.
- User inputs "Lethbridge" for Departure Point, then it appears correctly in departure point combo box.
- User then inputs "Calgary" for Arrival Point, then it appears correctly in arrival point combo box.
- User then inputs "January 5, 1996" for Departure Date, then it appears correctly in the associated combo box.
- User then inputs "1330" for Departure Time, then it appears correctly in the associated combo box.
- User then inputs "January 5, 1996" for Arrival Date, then it appears correctly in the associated combo box.
- User then inputs "1500" for Arrival Time, then it appears correctly in the associated combo box.
- User then inputs "250" for Distance, then it appears correctly in the associated combo box.
- User then inputs "75.75" for First Class Price, then it appears correctly in the associated combo box.
- User then inputs "50.21" for Second Class Price, then it appears correctly in the associated combo box.
- User then inputs "43.89" for Third Class Price, then it appears correctly in the associated combo box.
- User then inputs "Sally" for airplane name. then it appears correctly in the associated combo box.
- User then pushes add button and is asked if they want to add this new record for confirmation.
- User selects yes and then record is added to the flight table in the database.
- User is then brought back to main screen.
Case2: (arrival date prior to departure date)
- User pushes flight tab in main menu then the sub flight menu appears.
- User then selects add tab in flight sub menu and a screen appears with all the empty flight fields, except a Flight Number field which will be assigned by the computer.
- User inputs "Paris" for Departure Point, then it appears correctly in departure point combo box.
- User then inputs "Nowhere" for Arrival Point, then it appears correctly in arrival point combo box.
- User then inputs "February 2, 1996" for Departure Date, then it appears correctly in the associated combo box.
- User then inputs "0130" for Departure Time, then it appears correctly in the associated combo box.
- User then inputs "February 3, 1996" for Arrival Date, then a error message appears on the screen saying "arrival date occurs before departure date" and User is prompted to change their input. User then puts "February 4, 1996", then it appears correctly in the associated combo box.
- User then inputs "0000" for Arrival Time, then it appears correctly in the associated combo box.
- User then inputs "77821" for Distance, then it appears correctly in the associated combo box.
- User then inputs "1500.00" for First Class Price, then it appears correctly in the associated combo box.
- User then inputs "907.65" for Second Class Price, then it appears correctly in the associated combo box.
- User then inputs "876.02" for Third Class Price, then it appears correctly in the associated combo box.
- User then inputs "Jonny Boy" for the Airplane Name then it appears correctly in the associated combo box.
- User then pushes add button and is asked if they want to add this new record for confirmation.
- User selects yes and then record is added to the flight table in the database.
- User is then brought back to main screen.
Case3: (invalid distance and unavailable plane entered)
- User pushes flight tab in main menu then the sub flight menu appears.
- User then selects add tab in flight sub menu and a screen appears with all the empty flight fields, except a Flight Number field which will be assigned by the computer.
- User inputs "Flin Flon" for Departure Point, then it appears correctly in departure point combo box.
- User then inputs "Cardston" for Arrival Point, then it appears correctly in arrival point combo box.
- User then inputs "July 4, 1996" for Departure Date, then it appears correctly in the associated combo box.
- User then inputs "1500" for Departure Time, then it appears correctly in the associated combo box.
- User then inputs "July 7, 1996" for Arrival Date, then it appears correctly in the associated combo box.
- User then inputs "0030" for Arrival Time, then it appears correctly in the associated combo box.
- User then inputs "778721" for Distance, then an error message box appears saying "distance is too great of a value", user is then prompted to change their value. User then input "-459", an error message box appears saying that "This is an invalid flight distance, must be a positive value". The user is the prompted to change their input. The user then puts "5001", then this value appears correctly in the associated combo box.
- User then inputs "806.00" for First Class Price, then it appears correctly in the associated combo box.
- User then inputs "506.65" for Second Class Price, then it appears correctly in the associated combo box.
- User inputs "490.90" for Third Class Price, then it appears correctly in the associated combo box.
- User then inputs "Big Red" for Plane name, then an error message appears saying "This plane is not available at this flight time!", the user is then prompted to change their input. The user then puts "Lizard" in the combo box, then it appears correctly in the associated combo box.
- User then pushes add button and is asked if they want to add this new record for confirmation.
- User selects yes and then record is added to the flight table in the database.
- User is then brought back to main screen.
Case4: (second class ticket price is more expensive than first)
- User pushes flight tab in main menu then the sub flight menu appears.
- User then selects add tab in flight sub menu and a screen appears with all the empty flight fields, except a Flight Number field which will be assigned by the computer.
- User inputs "Montreal" for Departure Point, then it appears correctly in departure point combo box.
- User then inputs "Toronto" for Arrival Point, then it appears correctly in arrival point combo box.
- User then inputs "September 15, 1996" for Departure Date, then it appears correctly in the associated combo box.
- User then inputs "1900" for Departure Time, then it appears correctly in the associated combo box.
- User then inputs "September 16, 1996" for Arrival Date, then it appears correctly in the associated combo box.
- User then inputs "0417" for Arrival Time, then it appears correctly in the associated combo box.
- User then inputs "985" for Distance, then it appears correctly in the associated combo box.
- User then inputs "378.15" for First Class Price, then it appears correctly in the associated combo box.
- User then inputs "450.00" for Second Class Price, then a error message box appears stating that "the second class price is more expensive than the first class ticket price", the user is then prompted to change their input value. The user then inputs "-980", an error message box appears stating "an invalid price has been entered", the user then is prompted to change their input and inputs "300.00", then it appears correctly in the associated combo box.
- User then inputs "255.46" for Third Class Price, then it appears correctly in the associated combo box.
- User then inputs "Blue Boy" for Plan name, then it appears correctly in the associated combo box.
- User then pushes add button and is asked if they want to add this new record for confirmation.
- User selects yes and then record is added to the flight table in the database.
- User is then brought back to main screen.
Case5: (all valid inputs, but user cancels add)
- User pushes flight tab in main menu then the sub flight menu appears.
- User then selects add tab in flight sub menu and a screen appears with all the empty flight fields, except a Flight Number field which will be assigned by the computer.
- User inputs "Lethbridge" for Departure Point, then it appears correctly in departure point combo box.
- User then inputs "Calgary" for Arrival Point, then it appears correctly in arrival point combo box.
- User then inputs "January 5, 1996" for Departure Date, then it appears correctly in the associated combo box.
- User then inputs "1330" for Departure Time, then it appears correctly in the associated combo box.
- User then inputs "January 5, 1996" for Arrival Date, then it appears correctly in the associated combo box.
- User then inputs "1500" for Arrival Time, then it appears correctly in the associated combo box.
- User then inputs "250" for Distance, then it appears correctly in the associated combo box.
- User then inputs "75.75" for First Class Price, then it appears correctly in the associated combo box.
- User then inputs "50.21" for Second Class Price, then it appears correctly in the associated combo box.
- User then inputs "40.00" for Third Class Price, then it appears correctly in the associated combo box.
- User then inputs "Prince of Pumpernickle" for Plane Name, then it appears correctly in the associated combo box.
- User then pushes add button and is asked if they want to add this new record for confirmation.
- User selects no and then the screen with the input fields is shown again. The user pushes cancel and the main menu is shown to the user, all entered data has been lost.

Test modify option

Enter an existing Flight Number.
This will test the search facility of this function.
The result should be displaying of the selected flight on the screen.
Enter a non-existant Flight Number.
This will test the search facility of this function.
The result should be displaying of an empty list box and error message.
Enter an existing Flight Number, and modify the departure date to one day in the future.
This will test the update facility of this function.
The result should be an updated entry in the Flight Table.
Enter the same Flight Number as in previous test.
This will test the previous operation to see if the Flight Table was modified correctly.
The result should be displaying the updated entry on the screen.
Enter an existing Flight Number and modify the departure date to one day previous from the current date.
This will test the error detection of invalid dates.
The result should be displaying of an error message and returning to the Modify Flight screen.
Enter the same Flight Number as in previous test.
This will test to make sure that the entry was not modified by the Test 5.
The result should be displaying of the same unmodified flight data.
Enter an existing Flight Number and change the First Class Price to a value lower than the Second Class Price.
This will test the error detection of the price fields.
The result should be an error message when the user selects Modify.
Enter an existing Flight Number and change the Distance to a negative value.
This will test the error detection of the distance field.
The result should be an error message when the user selects Modify and the table remaining unchanged.
Enter an existing Flight Number and attempt to modify the Flight Number.
This will test the unmodifiability of the Flight Number field.
The result should be no change to the record since this field is displayed only and not modifiable.

More tests, such as those found in the Add Flight Section can be added here if necessary.

Test Delete Option
- Case1: (user knows flight number)
  - User pushes flight tab in main menu then the sub flight menu appears.
  - User then selects delete tab in flight sub menu and a screen appears with all the empty flight fields.
  - User types in known Flight Number. All the fields appear full because the computer has located the flight from the flight table in the database.
  - User pushes delete and confirmation screen is displayed asking "Do you really want to delete this flight?".
  - User selects yes and then the record is removed from the database and the user is brought back to the main screen.
- Case2: (user doesn't know flight number)
  - User pushes flight tab in main menu then the sub flight menu appears.
  - User then selects delete tab in flight sub menu and a screen appears with all the empty flight fields.
  - User types in incorrect Flight Number. Computer then displays a error message box stating "Flight number is not in the database". The user is then put back into the entry screen.
  - User then enters "January 2, 1996" for Departure Date. The combo box listings then become shorter and the user then scrolls down the flight number combo box and selects a flight number. All the fields then become filled with that particular flight info.
  - User pushes delete and confirmation screen is displayed asking "do you really want to delete this flight?".
  - User selects yes and then the record is removed from the database and the user is brought back to the main screen.
- Case3: (user cancels delete)
  - User pushes flight tab in main menu then the sub flight menu appears.
  - User then selects delete tab in flight sub menu and a screen appears with all the empty flight fields.
  - User types in known Flight Number. All the fields appear full because the computer has located the flight from the flight table in the database.
  - User pushes delete and confirmation screen is displayed asking "do you really want to delete this flight?". User selects no and then the record is left in the database from the database and the user is brought back to the input fields screen with same fields filled as before.
  - User selects cancel and is the asked for confirmation.
  - User agrees and then is brought back to the main menu.
Booking agents
- Test Cancel option
- Test Delete option
  - select an agent
  - delete it
- Test Modify option
  - For each field:
    - Select a (valid) agent
    - Blank the field
    - Click on 'Modify'
  - Test each of these by clicking on 'Modify' after changing:
    - Select an agent
      
      Add digit to surname
      Add digit to first name
      change login to one already in use
      Add digit to login name
      Enter new password with digit
- Test 'Add' option
  - Select a (valid) agent
  - Try to 'add' it, as is
  - Select 'new'
Aircraft
- Test Cancel option
- Test Delete option
  - select a plane
  - delete it
- Test Modify option
  - For each field:
    - Select a (valid) plane
    - Blank the field
    - Click on 'Modify'
  - Test each of these by clicking on 'Modify' after changing:
    - Select a plane
      
      Delete one of the letters in 'window columns'
      Add a letter to 'window columns'
      Add an invalid character to 'window columns'
      Add or subtract a letter from 'aisle columns'
      Add an invalid character to 'aisle columns'
      Add a letter from 'aisle columns' to 'centre columns'
      Add a letter from 'window columns' to 'centre columns'
      Add an invalid character to 'centre columns'
    - For each class:
      
      Change the 2nd number:
      
      To be negative
      To equal the 1st number
      To be one less than the 1st number
      To be equal to the next class' 1st number
      To be one less than the next class' 1st number
      
      Change the 1st number:
      
      To be negative
      To be equal to the previous class' 2nd number
      To be one more than the previous class' 2nd
- Test 'Add' option
  - Select a (valid) plane
  - Try to 'add' it, as is
  - Select 'new'
Booking Agent Sub-system Module Testing

Booking Agent sub-system tests will use the initial database values specified at the end of this document. All tests start by logging in to the Booking Agent Sub-system as 'test'.

Modify Booking
- add another passenger as in the previous test
- choose Lethbridge as the depature city
- flight ff001 will be greyed out since it is now full
Query Passenger
Query Flight
Boarding Pass
Initial database values for testing

Agent Table:
Surname First Name Initial Test_surname Test_First T Address Phone 555 120 st Calgary (403) 555-4321 Login Password test test (encrypted)
Airplane Table:
Plane Name Manufacturer largetest PlanerU smalltest PlanerU Window Columns Aisle Columns Center Columns A,E C,D B A,D B,C - (none) 1st Class Rows 2nd Class Rows 3rd Class Rows 1-2 3-4 5-7 1 2 3
Flight Table:
Flight Number Depature Date Depature Time Depature City ff001 January 1, 1996 1030 Lethbridge ff002 March 15, 1996 0000 Flin Flon ff003 May 25, 1996 0900 Ottawa ff004 July 4, 1996 0130 Tokyo ff005 January 9, 1996 1030 Lethbridge Arrival Date Arrival Time Arrival City Distance January 1, 1996 1100 Calgary 200 March 17, 1996 0700 New York 1400 May 25, 1996 1700 Vancouver 1700 July 6, 1996 1500 London 3500 January 9, 1996 1100 Calgary 200 1st Class Fare 2nd Class Fare 3rd Class Fare Plane Type 120.00 100.75 80.75 smalltest 306.95 250.00 225.00 smalltest 412.00 385.63 337.87 largetest 1120.03 976.10 955.10 largetest 120.00 100.75 80.75 smalltest
Passenger Table:
Last Name First Name Address City Grieg Mark 7 23 st SW Calgary Grete Don 8 23 st SW Calgary Hersh David 99 45 ave NE Calgary Holoua James 34 43 ave NE Calgary Kellam Pamela 32 8 ave NE Calgary MacGown George 78 98 ave SE Ottawa Mellis Leagh 21 32 ave SE Ottawa Nadurak Hiz 2 8 st NE Ottawa Redwood Paul 4 1 st NW Ottawa Redwood Ali 4 1 st NW Ottawa Sarout Peter 34 98 st NW Vancouver Trudel Hiap 3 1 ave SE Vancouver Trudel John 8 2 ave SE Vancouver Wang Joseph 8 1 ave SE Vancouver Province Postal Code Phone Number Alberta T0H 2V5 (403) 555-1234 Alberta T0H 2V5 (403) 555-4321 Alberta T0H 2V5 (403) 555-9877 Alberta T0H 2V5 (403) 555-3451 Alberta T0H 2V5 (403) 555-4213 Ontario S0J 4G9 (613) 555-1234 Ontario S0J 4G9 (613) 555-4321 Ontario S0J 4G9 (613) 555-4214 Ontario S0J 4G9 (613) 555-8768 Ontario S0J 4G9 (613) 555-4214 British Columbia V8W 2T4 (604) 555-4218 British Columbia V8W 2T4 (604) 555-4532 British Columbia V8W 2T4 (604) 555-6879 British Columbia V8W 2T4 (604) 555-4323
Booking Table:
Flight Number Class Ticket Number ff001 1 001231 ff001 1 001232 ff001 1 001233 ff001 1 001244 ff001 2 001245 ff001 2 001236 ff001 2 001247 ff001 2 001238 ff001 3 001241 ff001 3 001242 ff001 3 001243 ff002 1 001249 First Name Last Name Phone Number Mark Grieg (403) 555-1234 Don Grete (403) 555-4321 David Hersh (403) 555-9877 James Holoua (403) 555-3451 Pamela Kellam (403) 555-4213 George MacGown (613) 555-1234 Leagh Mellis (613) 555-4321 Hiz Nadurak (613) 555-4214 Paul Redwood (613) 555-8768 Ali Redwood (613) 555-4214 Peter Sarout (604) 555-4218 James Holoua (403) 555-3451 Seat Number Seat Preference 1A Window 1B Window 1C Aisle 1D Window 2A Window 2B Aisle 2C Aisle 2D Center 3A Window 3B Aisle 3C Aisle 1B Aisle Special Vegetarian none Wheel chair none none none none none none none none none

Booking agents

Aircraft

Booking Agent Sub-system Module Testing

Modify Booking

Query Passenger

Query Flight

Boarding Pass

Initial database values for testing

Agent Table:

Airplane Table:

Flight Table:

Passenger Table:

Booking Table:

President's Message

Integration Tesing

System Administration Testing

Booking Agent Testing

Test data

President's Message

Integration Testing

System Administrtation Sub-system Module Testing

Flights