Unit testing

Login Procedure

Black Box Testing:
Tests:

1. Ensure that user is required to supply both a valid username, and that usernames corresponding password to gain access to the system.

2. Ensure that users with Front Desk access may only select the front desk screen from login screen.

3. Ensure that users with Kitchen access may only select the Kitchen Desk screen from login screen.

4. Ensure that users with Administration access may select any of the screens from login screen.

Front Desk

Leave Message

Black Box Testing:
Tests:

1. Ensure that only valid room numbers which are currently occpuied may be selected.

2. Ensure that the guest is in the room selected.

3. Ensure that the proper time is set.

4. Ensure message buffer cannot be overflowed.

5. Ensure Time Stamp may not be altered.

6. Ensure message is actualy saved, and no empty messages.

7. Ensure there is a message sender.

Customer Reservation

Black Box Testing:
Tests:

1. Ensure that Checkin date must be less than check out date.

2. Ensure Number of guests must be >= 1

3. Ensure Number in party must be > = 1

4. Ensure phone number must be a valid phone number format

5. Ensure All possible rooms are returned in searches, this will be done by dooing small examples by hand first, and then ensuring that the software returns the correct results.

6. Ensure CheckIn/CheckOut dates are larger then current date when initally entered.

7. Ensure that Special Instruction Buffer cannot be overflowed.

8. Ensure that a room that is reserved, actually is, aswell as when a customer is accepted, it is actually fulled.

Kitchen Module

Room Service Request

Black Box Testing:
Tests:

1. Verify the math on a series of possible orders.

2. Ensure that you cannot change an order to something that is not on the menu.

3. Ensure that it is not possible to edit prices.

4. Ensure that order time is automaticly entered correctly.

5. Ensure delivery time is greater that order time.

6. Ensure room number corresponds to a room that is occupied.

7. Ensure menu corresponds to the menu that is input in the administrative module.

Adminstrative Module

Taxes

Black Box Testing:
Tests:

1. Ensure that there are no negative tax rates.

2. Ensure tax rates are numeric values.

Employee Administration

Black Box Testing:
Tests:

1. Ensure employee numbers are unique.

2. Ensure that you must have adminstrative access to view and change this screen.

Report Generation

Black Box Testing:
Tests:

1. Ensure that you cannot select a report that does not exist.

2. Ensure that if end date is less than start date the system does something appropriate.

Edit Kitchen Menu

Black Box Testing:
Tests:

1. Ensure that prices are positive values.

2. Ensure that you cannot overflow either of the item or description buffers and that the input is text of some form.

Integration Testing

Security Testing

We are address internal security issues to the Hotel Management System, as there will be no access to the system from outside the hotel. Issues of Concerns will be that unauthorized staff, or other intruders will not be able to gain unauthorized access to the system, or subsystems. Testing will involve insuring that any systems that fall under administration can only be accessed by Administration users. Then Secondly that the other systems can only be accessed by appropriately authorized perosnel. Finaly we will ensure that the data files themselves will be able to be accessed only by people with the corresponding access which would be availabe through the hotel management system.

To Be Finished By: March 22, 1996

Stress Testing

We will ensure that the system is able to maintain large numbers of customer, and billing records in the system. As well as being able to handle large numbers of reservations, and concurrent users. This will ensure that even during your peak times the system will not fail, or slow to a unacceptable level. The results of this test will also enable us to properly deterimine the minimum hardware requirements thats should reasonably be considered.

This will be accomplished by designing tests that put unrealisticly high loads on the system, stressing limits of memory, and transaction processing, as well as printing queues.

To Be Finished By: March 23, 1996

Performance Testing

We will test to ensure that response time for all real time components of the system perform to acceptable levels.

This will be done by simulating normal usage in our labs, to ensure that no one is ever left waitting for unreasonable time periods.

To Be Finished By: March 24, 1996

Recovery Testing

We will test the time it will take to have your system up and running again, if for some unforceable reason your system halts. These tests will involve cutting power to the system, determining data loss, and re-entry times, as well as reinitialization times before the whole system can be brought back up to both an acceptable levelof functionality , and a normal level of functionality.

To Be Finished By: March 25, 1996

Validation Testing

This is the test which determines whether or not the product meets our customers requirements. This will be done at the final presentation for the 451 group demos. Wel will be putting the system through a series of black box tests, which demonstrate conformity with our customers requirements. This will also include a review of documentation, ensuring that it is correct, and it meets the customers needs. Finally we shall ensure that all functional requirements are met.

To Be Finished By: Date to be scheduled, by Dr. Shaw