... | ... | @@ -253,76 +253,58 @@ Refer to the section of "Acceptance Test Results"<br> |
|
|
**Acceptance Test Results**
|
|
|
-----------------------------
|
|
|
**Testing of User Stories:**
|
|
|
* *Following the order of the above*
|
|
|
* *Following the order in the section User Stories Implemented*
|
|
|
|
|
|
* 1. Searching for flight routes: null, existing, non-completed, completed, duplicate, etc.<br>
|
|
|
* 2. Retrieval of reservation: retrievable, correct, incorrect, multiple, etc.<br>
|
|
|
* 3. Usability of web pages: general web application testing will be applicable here. <br>
|
|
|
* 4. Origin Time Indication: check if both origin time displaying or not, the correctness of the time, etc.<br>
|
|
|
* 5. Displaying search results: check if the results will show up or not, the correctness of the results, etc. <br>
|
|
|
* 6. Language options of pages: Check if language choices exist, choices are clickable or not, etc.* <br>
|
|
|
* 7. Security of payment page: check if payment information still exist in database or not, etc. <br>
|
|
|
* 8. About page of the company: Responsiveness, completeness, etc.<br>
|
|
|
<br>
|
|
|
|
|
|
From M3???
|
|
|
**Eight User with Acceptance Tests and Estimates**<br>
|
|
|
Estimates made on a scale of 1-5.<br>
|
|
|
* 1. Searching for flight routes: null, existing, non-completed, completed, duplicate, etc.<br>
|
|
|
|
|
|
**1. As a customer, I want to be able to easily search for flights based on the desired destination, origin, departure date/time so I can book flights with minimal technological ability.**
|
|
|
<br>
|
|
|
|
|
|
Acceptance Tests: <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."
|
|
|
* Search for something that should not exist in the, for example, "beans."
|
|
|
<br>
|
|
|
|
|
|
**2. As a new customer, I want an “About” section where I can learn about the company before I book with them so I can feel more connected and develop trust.**
|
|
|
<br>
|
|
|
|
|
|
* 2. Retrieval of reservation: retrievable, correct, incorrect, multiple, etc.<br>
|
|
|
|
|
|
Acceptance Tests:<br>
|
|
|
* Ensure there is a working, visible option from every screen to go the "About" page.
|
|
|
* The "About" page has marked sections that explain the history of the company and its goals.
|
|
|
* 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.
|
|
|
<br>
|
|
|
|
|
|
**3. As a customer, I want to know that my financial information is secure when booking a flight, so I’m not concerned about my information being leaked.**
|
|
|
|
|
|
|
|
|
|
|
|
* 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.
|
|
|
<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 a message pops up indicating that the payment is secured and the information has been deleted.
|
|
|
* Check that the payment information is not anywhere in the database.
|
|
|
* 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>
|
|
|
|
|
|
**4. As a customer, I would like to know the exact trip length and the exact final price before booking, so I have a sense of awareness.**
|
|
|
<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.
|
|
|
<br>
|
|
|
|
|
|
**5. As a customer, I would like to see all of the details related to my reservation including terminal number, luggage added, booking reference, etc. so check-ins are easier and I feel prepared**
|
|
|
<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.
|
|
|
<br>
|
|
|
|
|
|
**6. As a customer, I want a website that is visually appealing and doesn’t require any extra digging for information, so I can save time and effort.**
|
|
|
<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.
|
|
|
<br>
|
|
|
* 6. Language options of pages: Check if language choices exist, choices are clickable or not, etc.* <br>
|
|
|
|
|
|
**7. As a customer, I want different language options so I can choose a language I’m most comfortable with.**
|
|
|
<br>
|
|
|
|
|
|
Acceptance Tests:<br>
|
|
|
* Test if the user can select the language they want from a dropdown menu.
|
... | ... | @@ -330,13 +312,21 @@ Acceptance Tests:<br> |
|
|
* The pages are translated correctly
|
|
|
<br>
|
|
|
|
|
|
**8. As a customer, I want to see the current time at my origin/destination and what time it will be when I arrive, so I can plan my trip accordingly.**
|
|
|
|
|
|
|
|
|
* 7. Security of payment page: check if payment information still exist in database or not, etc. <br>
|
|
|
Acceptance Tests:<br>
|
|
|
* Test if a message pops up indicating that the payment is secured and the information has been deleted.
|
|
|
* Check that the payment information is not anywhere in the database.
|
|
|
<br>
|
|
|
|
|
|
|
|
|
* 8. About page of the company: Responsiveness, completeness, etc.<br>
|
|
|
<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.
|
|
|
* Ensure there is a working, visible option from every screen to go the "About" page.
|
|
|
* The "About" page has marked sections that explain the history of the company and its goals.
|
|
|
<br>
|
|
|
|
|
|
**Domain Diagram**
|
... | ... | |