... | ... | @@ -248,39 +248,34 @@ Refer to the section of "Acceptance Test Results"<br> |
|
|
**Acceptance Test Results**
|
|
|
-----------------------------
|
|
|
*Following the order in the section of* **User Stories Implemented**
|
|
|
* **1. Searching for flight routes**: null, existing, non-completed, completed, duplicate, etc.<br>
|
|
|
* **1. Searching for Flight Routes**: (null, existing, non-completed, completed, duplicate, etc.)<br>
|
|
|
|
|
|
* Search for a known destination/origin available; for example, "Saskatoon."<br>
|
|
|
* Search for a number that could be related to departure times, for example, "11:00" or "1800."<br>
|
|
|
* Search for something that should not exist in the, for example, "beans."<br>
|
|
|
|
|
|
* 2. Retrieval of reservation: retrievable, correct, incorrect, multiple, etc.<br>
|
|
|
Acceptance Tests:<br>
|
|
|
* Test if a confirmation page pops up displaying all the details related to the reservation once it is made.
|
|
|
* Check if the confirmation page has all the details required to be presented to the customer: such as name, date of birth, address, phone number, email, type of airplane, flight number, flight date and time, departure airport, destination airport, terminal number, booking reference.
|
|
|
* **2. Retrieval of Reservation**: (retrievable, correct, incorrect, multiple, etc.)<br>
|
|
|
* Test if a confirmation page pops up displaying all the details related to the reservation once it is made.<br>
|
|
|
* Check if the confirmation page has all the details required to be presented to the customer: such as name, date of birth, address, phone number, email, type of airplane, flight number, flight date and time, departure airport, destination airport, terminal number, booking reference.
|
|
|
<br>
|
|
|
|
|
|
* 3. Usability of web pages: general web application testing will be applicable here. <br>
|
|
|
Acceptance tests:<br>
|
|
|
* Test if the website is popped up and displayed properly
|
|
|
* Test if all the content of the website is displayed as required
|
|
|
* Test if all the content of the website is displayed as required and providing ease of use.
|
|
|
* Test if all the content of the website is displayed as required and providing ease of use, besides, meeting the general aesthetics standard.
|
|
|
* **3. Usability of Web Pages**: general web application testing will be applicable here. <br>
|
|
|
* Test if the website is popped up and displayed properly
|
|
|
* Test if all the content of the website is displayed as required
|
|
|
* Test if all the content of the website is displayed as required and providing ease of use.
|
|
|
* Test if all the content of the website is displayed as required and providing ease of use, besides, meeting the general aesthetics standard.
|
|
|
<br>
|
|
|
|
|
|
* 4. Origin Time Indication: check if both origin time displaying or not, the correctness of the time, etc.<br>
|
|
|
|
|
|
Acceptance Tests:<br>
|
|
|
* Test if the local time is displayed correctly.
|
|
|
* Test if the time at the desired destination is displayed properly.
|
|
|
* Test to see if the local time and the time at the destination when the user arrival is accurate.
|
|
|
* **4. Origin Time Indication**: check if both origin time displaying or not, the correctness of the time, etc.<br>
|
|
|
* Test if the local time is displayed correctly.
|
|
|
* Test if the time at the desired destination is displayed properly.
|
|
|
* Test to see if the local time and the time at the destination when the user arrival is accurate.
|
|
|
<br>
|
|
|
|
|
|
* 5. Displaying search results: check if the results will show up or not, the correctness of the results, etc. <br>
|
|
|
Acceptance Tests:<br>
|
|
|
* Check that the exact length and final price is visible to the user on the screen before booking.
|
|
|
* Make sure that the time lengths are not overlapping and are in the proper order.
|
|
|
* The time lengths correspond to the correct time zones.
|
|
|
* **5. Displaying search results**: check if the results will show up or not, the correctness of the results, etc. <br>
|
|
|
* Check that the exact length and final price is visible to the user on the screen before booking.
|
|
|
* Make sure that the time lengths are not overlapping and are in the proper order.
|
|
|
* The time lengths correspond to the correct time zones.
|
|
|
<br>
|
|
|
|
|
|
* 6. Language options of pages: Check if language choices exist, choices are clickable or not, etc.* <br>
|
... | ... | |