Assignment 3 – Test Case/Scenario Documentation
Students must prepare a comprehensive Test Case Report for the “Hotel Check-in/Check-out” application in full compliance with all the requirements listed below. You need to include at least two techniques for black box testing and at least three different non-functional tests. The system is being designed to work in a client/server environment at the front-desk at a hotel, using Microsoft technology (C#, .NET, SQL server, etc.)
The document should include:
1. Title Page (see Assignment 2 for details).
2. Table of Contents (with page numbers, automatically generated).
3. Description of the application (who, what, where, how): twoto three paragraphs.
4. Description of the test environmentto be used for the test (type of equipment, operating system etc., can be your own computer).
5. Summary of the testsplanned and the purpose of the testing. Provide a description of the test and why it is significant for this application.
6. An estimate of the level of effort (number of hours) that you think it will take to complete the testing (assume only 1 tester is available), including any assumptions you have made in making this estimate.
7. A description of the risks associated with the testing (minimum of three)
8. Test cases: List of test scenariosand test cases in a table (formatted correctly with an embedded Excel spreadsheet or a Microsoft table) including the following columns:
1. A sequential number.
2. The type of test (e.g., functional or non-functional) and within that the specific type.(e.g., boundary in black box)
3. The test scenario (what function or codeare you testing)
4. The data that you will enter to test this scenario (should include both a passing and a failing test case for each test scenario).
5. The expected result (if the system was working correctly).
6. A column for test results and a column for status (these are both blank)
The test cases should be presented in the order they will be run, with the functional before the non-functional.RESULTS ARE NOT REQUIRED
The document should include at least at least 10 test cases.
Sources of any other information used must be referenced.
Pages must be numbered and must include your name on each page.
Evaluation
Your report will be evaluated in each of the following ways:
1. Your test cases must be comprehensive and cover all of the functionality of the application (10 is just a guideline).
2. Your test cases and test scenarios must be clear and complete and they must be detailed enough so that they can be run by a tester other than yourself or in an automated environment.
3. Section 1 through 7 must be written in complete sentences and be grammatically correct in the third person.
4. Your test cases in Section 8 may be written in bullet form but must be written in good formal English (no contractions, etc.) and must be readable. If you Excel to format, attach the Excel spreadsheet separately.
5. You must following the instructions in the report format EXACTLY, it is a company standard.
6. You have the flexibility to “design” the document (e.g., typeface, font size, but your style must be consistent throughout the entire document and must be readable for the tester who will be conducting the tests later.
7. Your submission must be timely in terms of the deadline given in the syllabus.
8. You should spellcheck all parts of the document and auto-generate the table of contents.
Requirements Specified for Application
Develop a C# application that handles the check-in/check-out process at a terminal in the front desk of a hotel: The application should include the hotel’s logo, location, email, and telephone number on all screens and reports..
A guest will appear at the front desk for check-in. The clerk will ask if he has a reservation, If so, she will ask his name and check the system for the reservation. If he/she does not, the clerk asks for an ID and enters the name and address into the system from the ID. The guest is then asked for the type of room required and for a credit card that is validated by the clerk. If the credit card is good, the clerk will search the database for an open room that meets the requirements given. Once found, the guest is registered in that room and the number of days of occupancy reported to block the room from being reallocated while the guest is still there. The key is formulated and the guest shown the location of the room.
On checkout, the guest appears at the front desk and gives the clerk his/her room number. The clerk generates the bill and prints it out for the guest. The guest checks the invoice changes and then either authorizes payment from the credit card or asks for an item to be removed (e.g., his/her reservation included Wi-Fi and he was being charged separately). The room is marked in the system as empty so the housekeeping staff can begin the cleaning effort.
The hotel manager regularly generates reports on the occupancy rate of the hotel on a specific date as this is how his performance is monitored.
Guests are not very patient and so it is important that the process is efficient. There are several part-time clerks to ensure there is 24-hour coverage and so ease of use is another factor. Only authorized individuals are allowed to check-in and checkout guests. The clerks are not authorized to handle cash and if a credit card is not given then a manager must be called to handle any cash transaction on check-in or checkout.
Since credit card information is being entered as well as the name and address of the guest, security is important and so all transactions must be clearly labeled with the user name and the time of the transaction to provide a full audit trail. Users are required to use strong passwords (at last 8 characters) and to logout of the system when there are no guests in line..