Testing: Front Desk Functions

Tested functions are:

1. Reservation
2. Rooms
3. Add reservation
4. Delete reservation
5. Modify reservation
6. Search rooms
7. Find availability of rooms
8. Find guest in room
9. Guest
10. Add guest
11. Delete guest
12. Modify guest
13. Search guest
14. In Room
15. Check in
16. Check_Out
17. Print Invoice

1. Section: Reservation
   • Tests
     • Basic check to ensure all 5 options are accessablefor these security levels: manager and front desk. This is just a linkage test. Each of these options should take a user to the required menu.
2. Section: Rooms
   • Tests
     • Check the accessability of the menu items. This is just a linkage test.
3. Section: Add reservation
   • Tests
     • Check for return of an error in a message box for a day fully booked
     • Spot check for other days. They should either allow a booking (on a non-full day) or return an error stating that the day is full in a message box.
     • Add a new guest to a room on a non full day. This should return a success message box.
     • Book the above person into another room. This should also return a success message box.
     • Input invalid date(ie, June 31) this should return an error in a message box stating that the date is invalid.
     • Set the check out date before the check in date. Each of these should return an error in a message box.
     • Add too many occupants to a room. This should return an error in a message box informing the user that there are too many occupants.
     • All of the above errors should be compoundable. For example if an invalid date and an invalid check out date are set then the error message box should state that the date and the check out date are invalid.
4. Section: Delete Reservation
   • Tests
     • Try to delete nonexistant reservation number. This should return an error in a message box informing the user that they have attempted to delete a nonexistant reservation.
     • Try to delete the same reservation twice. This should return the same error as above.
     • Delete a normal reservation. This should return a success message box.
     • Delete an expired reservation. This should return a success message box.
5. Section: Modify Reservation
   • Tests
     • Since the inputs available are all the same please see 3 above.
6. Section: Search Rooms
   • Tests
     • Check to see that all menu options are accessable for the following security levels: management and front desk. This is just a linkage test.
7. Section: Find Availability of Rooms
   • Tests
     • Check availability of rooms on days set up as follows:
       1. All rooms free. Should return a message box reporting 200 rooms free.
       2. Some rooms free. Should return N rooms free, where N is a predefined number for the test. (ie, we have filled 200-N rooms)
       3. No rooms free. Should return a message box reporting 0 rooms free.
8. Section: Find Guest In Room
   • Tests
     • Check for a guest who has been checked in. This should return a dialog with the guest's room number.
     • Check for a guest who is booked into a room in the future. This should return a message box with the number of the room that they are going to be checked into, and the date that they are supposed to check in.
     • Check for a guest who has been checked out. This should return a message box stating that the guest is not, and will not be, checked into the hotel.
9. Section: Guest
   • Tests
     • Check to see that all menu options are access able for the following security levels: management and front desk. This is just a linkage test.
10. Section: Add Guest
    • Tests
      • Add a new guest. This should return a success message box.
      • Add an old guest (for the second time). This should return a message box informing the user that they guest already exists in the database.
      • Check invalid inputs for each possible input, for example an incorrect date. Each invalid input should return a message box informing the user which field was invalid. For example entering the date of June 31 1997 should return a message box stating that the date is incorrect. It should also handle compound errors, such as, an incorrect date and an invalid credit card number. It should return a message box stating that both the date and the credit card number are invalid.
11. Section: Delete Guest
    • Tests
      • Delete a guest. This should return a success message box.
      • Delete a non existant guest. This should return an error message box informing the user that they have attempted to delete a non existant guest.
12. Section: Modify Guest
    • Tests
      • Since the inputs available are all the same please see 10 above.
13. Section: Search Guest
    • Tests
      • Search for non existant room, last name, and id. Each of these should return a compound error message box and an individual error message box.
      • Search for existing guest. This should return the guests' data.
      • Search for a deleted guest. This should return the same error as a non existant guest.
14. Section: In Room
    • Tests
      • Check the linkage to the check in and check out functions. Each button should lead to it's repective lower level function.
15. Section: Check In
    • Tests
      • Check in a non existant guest. The function should call add guest, and after adding a guest and picking a room it should return a success message box.
      • Check in an existant guest. The function should call get reservation and should return a success message.
      • There is no way for this function to error. Only it's lower level functions should return error codes to the customer.
16. Section: Check Out
    • Tests
      • Check out a guest who has not checked in. This should produce an error message box stating that the guest has not yet checked in.
      • Check out a guest who was checked in. This should return a success message box.
17. Section: Print Invoice
    • Tests
      • Examine a print out of an invoice listing at least one of each possible item type. These include taxes, room service fees, telephone fees, room fee, etc.