Hotel Check-In/Check-Out Test Case
Hotel Check-In/Check-Out Test Case
Table of Contents
Description of Application............................................................................................................ 3
Test Environment......................................................................................................................... 3
Summary of Tests........................................................................................................................ 3
Level of Effort............................................................................................................................... 3
Tests Cases................................................................................................................................. 3
Description of Application
The application that is needed will be a C# application developed to help the hotel
handle the process of checking customers in and out at the front desk. The application
will allow the clerk to check to see if a quest has a reservation, search for available
rooms, check to make sure a credit card is valid, generates a bill upon check-out, and
marks the room empty after the guest checks out.
The clerks will also need to log-in and out of the system when depending on whether
guests are in line or not. Because of the amount of personal information that is entered
into this system, security is important and clerks must have strong passwords and all
transactions must be labeled with the clerk’s username and the time of the transaction.
Test Environment
The test environment will involve the use of a computer similar to the system used at
the hotel’s front desk. The computer will run on a Windows 7 operating system.
Summary of Tests
I will test the clerks’ ability to log in and out of the system quickly and efficiently; the ability to
create an account with a valid password, ensuring that an occupied room is marked as such
and a vacant room is marked “vacant”. I will also be testing to ensure that the security
components are present; for example, the manager is the only one who can handle cash, and
clerks are required to log-in and out of the system.
Level of Effort
These tests will not take a lot of time because they do not include testing the code. They are
mainly end-user tests in order to ensure that the software is functioning correctly.
Tests Cases
Test Test Test data Expected result Test Status
ID scenario results
1 Log-in Passing: Username: ddavis Passing: Clerk is
Password: (user able to log
password) in and is
Failing: Username: directed to
ddavis768 the check-
Password: (user in screen.
password) Failing: Error
message is
displayed
asking
clerk to try
again.
2 Log-out Passing: Clerk clicks “log- Passing: Clerk is
out” button logged out
Failing: Clerk clicks “log- and
out” button redirected
to the
home
screen.