Test and Evaluation Plan

5.1 Introduction - Objectives of the Test Plan:

5.2 Test Schedule - list of tests, dates and people responsible:

5.3 Detail of Testing, Monitoring, Reporting and Correcting Procedures:

The integration tests will be carried out by the programmer together with one of the the test coordinators and one member of the user manual group. This ensured tighter monitoring and the user manual group can gain insight of the function module groups.

The test coordinators will be responsible for monitoring and keeping track of all testing. Specifically, they will ensure that scheduled tests are carried out on time, keep all testing reports, and determine re-testing dates with the implementation group.

5.4 Proposed Dates for Submission of Individual Test Reports:

5.5 A short defense of our integration plan:

5.6 Discussion - details of the test plan with objectives and success criteria:

5.6.1 Unit Testing:

5.6.1.1 Add Ward:

• Objective:

  Ensure that the program is able to write the data entered by the user correctly into the database. The data entered at this stage will be used for unit testing of other modules.

• Tests:

  The tester must ensure manually that the data entered is stored correctly in the database. The program also must catch invalid inputs from the user, such as a ward that already exists in the database.

5.6.1.2 Change Ward:

• Objective:

  Ensure that any changes made by the user is reflected in the database.

• Tests:

  Enter a ward number that is not in the database. The system should respond by prompting the user to either reenter the ward number or exit from the function.

  Enter a valid ward number, then enter the same ward information as already exists in the database for this ward. The system should notify the user that there does not seem to be any changes to the ward information, and ask the user to enter new information of to exit from this function.

  Enter a valid ward number, and make some changes to the ward information. However, some of the input fields should be syntactically incorrect (e.g. an alphabetic string in a field that only accepts numbers). The system should respond by asking the user the reenter the information or to exit the function.

  Enter a valid ward number, and make some (valid) changes to the ward information. The tester must manually verify that the changes are reflected in the database.

5.6.1.3 Delete Ward:

• Objective:

  Ensure that the system can successfully find and remove a ward from the database. Also, ensure that syntactically incorrect input is detected.

• Tests:

  Enter a ward number that is not in the database, or that is syntactically incorrect (e.g. it contains a letter or other invalid symbol). The system should respond by asking the user to reenter the ward number, or to exit the function.

  Enter a ward number where rooms are currently in use. The system should ask the user to reenter the ward number or the exit from the function.

  Enter a valid ward number. The system should ask for confirmation to delete the ward. If confirmation is given, the ward should be removed from the database.

5.6.1.4 Update Staff:

• Objective:

  Ensure that any changes made by the user to staff information is reflected in the database. Also, ensure that syntactically incorrect input in any field is detected.

• Tests:

  Enter a staff number that is not in the database. The system should prompt the user to either reenter the staff number or to exit the function.

  Enter a staff name that is not in the database. The system should prompt the user to either reenter the staff name or to exit the function.

  Enter a valid staff number or a valid staff name. Make changes to the staff information--but make some of the fields syntactically incorrect. The system should prompt the user to reenter the information.

  Enter a valid staff number or a valid staff name. Make valid changes to the staff information. The system should ask for confirmation to make changes to the database. If confirmation is given, the changes should be written to the database. The tester should use the Display Staff function or manually verify that the changes have taken place.

5.6.1.5 Display Staff:

• Objective:

  Ensure that the system is able to retrieve staff information from the database and to display it on the screen.

• Tests:

  Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit from the function.

  Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit from the function.

  Enter a valid staff name or staff number. The information for that staff member should be displayed on the screen.

5.6.1.6 Hire Staff:

• Objective:

  Ensure that the system is able to add a new staff member to the database.

• Tests:

  Enter some syntactically incorrect data for the new staff member. The system should ask the user to reenter the data or to exit from the function.

  Enter staff information for a staff member already in the database. The system should ask the user to reenter the staff information or to exit the function.

  Enter valid staff information. The tester should then use the Display Staff function or manually verify that the database is updated correctly.

5.6.1.7 Terminate Staff:

• Objective:

  Ensure that the system is able to remove staff members from the database.

• Tests:

  Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit the system.

  Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit the system.

  Enter a valid staff number or name. The system should ask for confirmation from the user to delete the staff member from the database. If confirmation is given, the staff member should be removed from the database. The tester should use the Display Staff function or manually verify that the database is updated correctly.

5.6.1.8 Display Patient:

• Objective:

  Ensure that the system is able to retrieve patient information and display it on the screen.

• Tests:

  Enter a patient number that is not in the database. The system should respond by asking the user to reenter the patient number or to exit from the function.

  Enter a patient name that is not in the database. The system should ask the user to reenter the patient name or to exit from the function.

  Enter a valid patient number or name. The system should display the information relevant to that patient on the screen.

5.6.1.9 Admit Patient:

• Objective:

  Ensure that the system is able to add a new patient to the database.

• Tests:

  Enter the patient information, but make some of the fields syntactically incorrect. The system should prompt the user to either reenter the patient information, or to exit the function.

  Enter patient information for a patient who is already receiving treatment at the hospital. The system should ask the user to either reenter the patient information or to exit from the function.

  Enter valid patient information. If there are no rooms available at the hospital, the system should ask the user if the patient should be put on the waiting list. Otherwise, the patient is added to the database.

5.6.1.10 Discharge Patient:

• Objective:

  Ensure that the system is able to remove a patient from the database.

• Tests:

  Enter a patient name that is not in the database. The system should ask the user to reenter the patient name or to exit from the function.

  Enter a patient number that is not in the database. The system should ask the user to reenter the patient number or to exit from the function.

  Enter a valid patient name or patient number. Enter the discharge date. A discharge notification will be produced.

5.6.1.11 Update Patient:

• Objective:

  Ensure that the system is able to change patient information in the database.

• Tests:

  Enter a patient name that is not in the database. The system should ask the user to reenter the patient name or to exit from the function.

  Enter a patient number that is not in the database. The system should ask the user to reenter the patient number or to exit from the function.

  Enter a valid patient name or number. Enter an invalid treatment number. The system should ask the user to reenter the treatment number or to exit from the function.

  Enter a valid patient name or number. Enter a valid treatment number. Enter a new room number for the patient that is not available. The system should ask the user to enter another room number, or to exit from the function.

  Enter a valid patient name or number. Enter a valid treatment number. Enter a new room number for the patient. Enter the changed patient information. The system should ask the user for confirmation to make changes to the database. If confirmation is given, the changes are written to the database.

5.6.1.12 Generate Two Week Notification:

• Objective:

  Ensure that the system is able to generate the necessary two-week notifications required.

• Tests:

  Generate two-week notifications. The tester must manually verify that the correct notices are being generated from the database.

5.6.1.13 Add Shift:

• Objective:

  Ensure that the system is able to add a new shift to the ward schedule.

• Tests:

  Enter an invalid date. The system should ask the user to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid start time for the shift. The system should ask the user to reenter the start time or to exit from the function.

  Enter a valid date. Enter a valid start time. Enter an invalid end time. The system should ask the user to reenter the end time or the exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a ward number that does not exist in the hospital. The system should ask the user to reenter the ward number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid ward number. Select the a staff title for the shift. If the staff title is not suited for this shift, the system should ask the user to reenter the staff title or to exit from the function. If there is no supervising nurse with the correct specialty during that shift, the user is prompted to continue adding shifts until this condition is satisfied. Similarly, if there are not enough doctors and nurses during this shift, the user is prompted to continue adding shifts.

5.6.1.14 Copy Shift:

• Objective:

  Ensures that the system is able to copy information from an existing shift.

• Tests:

  Enter an invalid date. The user should be prompted to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid start time for the shift. The user should be prompted to reenter the start time or to exit from the function.

  Enter a valid date. Enter a valid start time. Enter an invalid end time. The system should prompt the user to reenter the start time or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a ward number that does not exist in the hospital. The system should prompt the user to reenter the ward number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid ward number. Enter an invalid date range to copy. The system should prompt the user to reenter the date range or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid ward number. Enter a valid date range. The shifts should be automatically copied into the database.

5.6.1.15 Delete Shift:

• Objective:

  Ensure that the system is able to remove a shift from the database.

• Tests:

  Enter an invalid date. The user should be prompted to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid start time. The system should prompt the user to reenter the start time or to exit from the function.

  Enter a valid date. Enter a valid start time. Enter an invalid end time. The system should prompt the user the reenter the end time or to exit from the system.

  Enter a valid date. Enter valid start and end times. Enter a ward number that does not exist in the hospital. The system should prompt the user to reenter the ward number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid ward number. The system should ask for confirmation from the user to remove the shift from the database. If confirmation is given, the system should delete the shift.

5.6.1.16 Display O/R Schedule:

• Objective:

  Ensure that the system is able to retrieve the correct O/R schedule and display it on the screen.

• Tests:

  Enter an Operation ID that does not exist. The system should prompt the user to reenter the Operation ID or to exit from the function.

  Enter a valid Operation ID. The system should display the O/R schedule related to that ID.

  Enter an invalid date. The system should prompt the user to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid time. The system should prompt the user to reenter the time or to exit from the function.

  Enter a valid date. Enter a valid time. The system should display the O/R schedule related to the date and time.

  Enter an Operating Room number that does not exist. The system should prompt the user to reenter the Operating Room number or to exit from the function.

  Enter a valid Operating Room number. The system should display the O/R schedule related to the Operating Room number.

  Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit from the function.

  Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit from the function.

  Enter a valid staff number or name. The system should display the O/R schedule related to the staff number or name.

  Enter a patient number that is not in the database. The system should prompt the user to reenter the patient number or to exit from the function.

  Enter a patient name that is not in the database. The system should prompt the user to reenter the patient name or to exit from the function.

  Enter a valid patient number or name. The system should display the O/R schedule related to the patient number or name.

5.6.1.17 Operating Schedule:

• Objective:

  Ensure that the system is capable of updating operating schedule information.

• Tests:

  Enter an Operation ID that does not exist. The system should prompt the user to reenter the Operation ID or to exit from the function.

  Enter a valid Operation ID. Make a change in the operating schedule. The system should ask for confirmation to write the change to the database. If confirmation is given, the database should be updated accordingly.

  Enter an invalid date. The system should prompt the user to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid time. The system should prompt the user to reenter the time or to exit from the function.

  Enter a valid date. Enter a valid time. Make a change in the operating schedule. The system should ask for confirmation to write the change to the database. If confirmation is given, the database should be updated accordingly.

  Enter an Operating Room number that does not exist. The system should prompt the user to reenter the Operating Room number or to exit from the function.

  Enter a valid Operating Room number. Make a change in the operating schedule. The system should ask for confirmation to write the change to the database. If confirmation is given, the database should be updated accordingly.

  Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit from the function.

  Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit from the function.

  Enter a valid staff number or name. Make a change in the operating schedule. The system should ask for confirmation to write the change to the database. If confirmation is given, the database should be updated accordingly.

  Enter a patient number that is not in the database. The system should prompt the user to reenter the patient number or to exit from the function.

  Enter a patient name that is not in the database. The system should prompt the user to reenter the patient name or to exit from the function.

  Enter a valid patient number or name. Make a change in the operating schedule. The system should ask for confirmation to write the change to the database. If confirmation is given, the database should be updated accordingly.

5.6.1.18 Operation:

• Objective:

  Ensure that the system is able to remove an operation from the database.

• Tests:

  Enter an Operation ID that does not exist. The system should prompt the user to reenter the Operation ID or to exit from the function.

  Enter a valid Operation ID. The system should ask for confirmation to remove the operation from the database. If confirmation is given, the database should be updated accordingly.

  Enter an invalid date. The system should prompt the user to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid time. The system should prompt the user to reenter the time or to exit from the function.

  Enter a valid date. Enter a valid time. The system should ask for confirmation to remove the operation from the database. If confirmation is given, the database should be updated accordingly.

  Enter an Operating Room number that does not exist. The system should prompt the user to reenter the Operating Room number or to exit from the function.

  Enter a valid Operating Room number. The system should ask for confirmation to remove the operation from the database. If confirmation is given, the database should be updated accordingly.

  Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit from the function.

  Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit from the function.

  Enter a valid staff number or name. The system should ask for confirmation to remove the operation from the database. If confirmation is given, the database should be updated accordingly.

  Enter a patient number that is not in the database. The system should prompt the user to reenter the patient number or to exit from the function.

  Enter a patient name that is not in the database. The system should prompt the user to reenter the patient name or to exit from the function.

  Enter a valid patient number or name. The system should ask for confirmation to remove the operation from the database. If confirmation is given, the database should be updated accordingly.

5.6.1.19 Operation:

• Objective:

  Ensure that the system is able to add a new operation to the database.

• Tests:

  Enter an invalid date for the operation. The system should prompt the user to reenter the date or to exit from the function.

  Enter a valid date. Enter an invalid start time for the operation. The system should prompt the user to reenter the start time or to exit from the function.

  Enter a valid date. Enter a valid start time. Enter an invalid end time for the operation. The system should prompt the user to reenter the end time or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a patient name that is not in the database. The system should prompt the user to reenter the patient name or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a patient number that is not in the database. The system should prompt the user to reenter the patient number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid patient name or number. Enter an invalid treatment number. The system should prompt the user to reenter the treatment number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid patient name or number. Enter a valid treatment number. Enter a staff name that is not in the database. The system should prompt the user to reenter the staff name or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid patient name or number. Enter a valid treatment number. Enter a staff number that is not in the database. The system should prompt the user to reenter the staff number or to exit from the function.

  Enter a valid date. Enter valid start and end times. Enter a valid patient name or number. Enter a valid treatment number. Enter a valid staff name or number. The system should ask for confirmation to book the operation. If confirmation is given, the database should be updated.

5.6.2 Integration Testing:

5.6.2.1 Maintenance Functions:

• Using the Add Ward Function, add the following wards to the hospital:
  Ward Number: 1 Description: Admit/Emergency Number of Rooms: 50 Ward Number: 2 Description: Operating Number of Rooms: 20 Ward Number: 3 Description: Geriatrics Number of Rooms: 50 Ward Number: 4 Description: Recovery Number of Rooms: 100 Ward Number: 5 Description: Intensive Care Number of Rooms: 50 Ward Number: 6 Description: Cardiology Number of Rooms: 50 Ward Number: 7 Description: Obstetrics Number of Rooms: 50 Ward Number: 8 Description: Pediatrics Number of Rooms: 50 Ward Number: 9 Description: Test Number of Rooms: 200

• Using the Change Ward function, change the number of rooms for ward 9 to 50.

• Using the Delete Ward function, delete ward 9.

5.6.2.2 Staff Administration Functions:

• Using the Hire Staff function, add the following staff member:
  Specialty: Pediatrics Title: Nurse First Name: Pat Last Name: Christensen Address: Box 361 Phone: 403 337 3108

• Use the Display Staff function to verify that the staff member was added to the database.

• Using the Update Staff function, change the title of the above staff member to "Nurse".

• Use the Display Staff function to verify that the staff member's title was updated.

• Use the Terminate Staff function to remove the staff member.

• Use the Display Staff function to verify that the staff member was deleted from the database.

5.6.2.3 Patient Administration Functions:

• Using the Admit Patient function, add the following patient:

  Ward: Pediatrics
  First Name: Joe
  Last Name: Ward
  Address: 84 Gallery Ave.
  City: Calgary
  Prov.: AB
  Pcode: T2N 1N4
  Phone: (416) 598-2248
  

• Use the Display Patient function to verify that the patient was added to the database.

• Use the Update Patient function to change the room number for the above patient to Room 23.

• Use the Display Patient function to verify that the Patient's information was updated.

• Use the Discharge Patient function to remove the patient.

• Use the Display Patient function to verify that the patient was deleted from the database.

5.6.2.4 Work/Ward Schedule Management:

• Using the Add Shift function, add the following shift to the shift schedule:

  Date: 10-Feb-96
  Ward: Geriatrics
  Shift: 2
  Doctor 1: Broten, Cedric
  Doctor 2: Thornton, David
  Nurse 1: Domanczuk, Taras
  Nurse 2: Pratt, Ian
  Nurse 3: Broten, Cedric
  

• Use the Copy Shift function to copy the above shift to the date 11-Feb-96.

• Use the Delete Shift function to delete the shift on 10-Feb-96.

5.6.2.5 O/R Scheduling Functions:

• Using the Book Operation function, add the following operation to the O/R Schedule:

  Date: 10-Feb-96
  Start Time: 12:30:00 PM
  End Time: 3:00:00 PM
  Patient: Birch, Randy
  Ward: Geriatrics
  Operating Room: 12
  Recovery Room: 67
  Doctor 1: Farrugia, John
  Doctor 2: Madill, John
  Nurse 1: Playfair, M.G.
  Nurse 2: Li, Derek
  

• Use the Display O/R Schedule function to verify that the operation was booked successfully.

• Use the Update Operating Schedule to change the Date of the above operation to 11-Feb-96.

• Use the Display O/R Schedule function to verify that the operation date was changed successfully.

• Use the Cancel Operation function to cancel the above operation.

• Use the Display O/R Schedule function to verify that the operation was successfully canceled.

5.6.3 Monitoring:

5.6.4 Reporting Procedures:

5.7 Summary of Individual Group Member Assignment for the Test Plan:

• Test Coordinators:
  1. Alex Tsang
  2. Chong Tang
• Unit Testers:
  1. Curtis Jenson
  2. Natalie Simpson
  3. Aaron Sun
  4. Pete Tozser
• Integration Testers:
  1. Dan Hay (Maintenance Functions)
  2. Darrell Nash (Staff Administration)
  3. Deb Howland (Staff Administration)
  4. Walid Labban (Patient Administration)
  5. Ed Stemler (Patient Administration)
  6. Dennis Yip (Work/Ward Schedule)

Last Modified Mar. 5, 1996 by

Darrell Nash