|
Milestone 7: Test Plan (i.e., QA plan) Due 7pm Friday, Feb 28, 2020<br>
|
|
**Quality Assurance Plan**<br>
|
|
• Quality Assurance Plan<br>
|
|
|
|
• Introduction - A brief description of the quality assurance strategies you are using<br>
|
|
|
|
• Scope - The features and requirements (functional and non-functional) that will be checked and those that will not be checked. Refer to FURPS+<br>
|
|
|
|
• Quality Objective - e.g., markers are able to run without it crashing and markers are able to use it with little guidance<br>
|
|
|
|
• Roles and responsibilities of team members<br>
|
|
|
|
• Test methodology - deliverables, strategies/approach (unit, regression, system/integration, acceptance), bug reporting, test tools<br>
|
|
|
|
• Inspection methodology - deliverables, strategies/approach (not graded)<br>
|
|
|
|
• Action Plan (as usual)<br>
|
|
|
|
|
|
|
|
|
|
Introduction - A brief description of the quality assurance strategies you are using<br>
|
|
|
|
|
|
|
|
Scope - The features and requirements (functional and non-functional) that will be checked and those that will not be checked. Refer to FURPS+<br>
|
|
|
|
|
|
|
|
|
|
|
|
**Storyboard**
|
|
|
|
<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.
|
|
|
|
|
|
Milestone 7: Test Plan Due February 28, 2020 (7:00pm Friday)
|
|
2. 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.
|
|
|
|
|
|
Create a test plan document.
|
|
3. 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.
|
|
|
|
|
|
**Action Plan**<br>
|
|
4. 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.
|
|
|
|
|
|
*Fantastic 4*:<br>
|
|
5. 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.
|
|
All team members had participated in two scheduled weekly meetings plus two additional meetings during the break, discussing details about this milestone and product alpha due in two weeks after the break.<br>
|
|
|
|
Time spent as a team: 6 hours (1.5 hours per team meeting, 4 meetings in total)
|
|
|
|
|
|
|
|
Ali: <br>
|
|
6. As a customer, I want different language options so I can choose a language I’m most comfortable with.
|
|
Drawed the sequence diagram and activity diagram with the team.<br>
|
|
|
|
Will create a database of the system for the next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 2 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Jordan: <br>
|
|
7. 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.
|
|
Scheduled and booked a team meeting room as a regular weekly task.<br>
|
|
|
|
Drawed the sequence diagram and activity diagram with the team.<br>
|
|
|
|
Will work closely with Ali on connections in the database for the next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 2 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Nick: <br>
|
|
8. 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.
|
|
Worked on Preliminary Implementation (Hello World App) on the departmental Virtual Machine plus Readme file documentation.<br>
|
|
<hr>
|
|
Will work closely with Ali on connections between HTML pages and database for next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 6 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Wes: <br>
|
|
|
|
Drafted up the sequence diagram, activity diagram and expanded UML diagram.<br>
|
|
|
|
Created Milestone 6 at Wiki and summarized Action Plan. <br>
|
|
|
|
Finished the final formatting of this milestone.<br>
|
|
|
|
Will work closely with Nick on connections between HTML pages and database for next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 5 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
|
|
|
|
**Preliminary Testing Plan**<br>
|
|
|
|
|
|
|
|
|
|
Quality Objective - e.g., markers are able to run without it crashing and markers are able to use it with little guidance<br>
|
|
|
|
|
|
|
|
Roles and responsibilities of team members<br>
|
|
|
|
|
|
|
|
Test methodology - deliverables, strategies/approach (unit, regression, system/integration, acceptance), bug reporting, test tools<br>
|
|
|
|
|
|
|
|
|
|
|
|
**Preliminary Testing Plan**<br>
|
|
* Testing approach:
|
|
* Testing approach:
|
|
* White-box testing
|
|
* White-box testing
|
|
* Black-box testing
|
|
* Black-box testing
|
|
|
|
|
|
* Testing levels:
|
|
* Testing levels:
|
|
* Unit testing
|
|
* Unit testing
|
|
* Integration testing
|
|
* Integration testing
|
|
* System testing
|
|
* System testing
|
|
* Operational acceptance testing
|
|
* Operational acceptance testing
|
|
|
|
|
|
* Testing types:
|
|
* Testing types:
|
|
* Installation testing
|
|
* Installation testing
|
|
* Compatibility testing
|
|
* Compatibility testing
|
... | @@ -72,28 +53,37 @@ Individual time will be spent on Milestone 7 & 8: 20 hours |
... | @@ -72,28 +53,37 @@ Individual time will be spent on Milestone 7 & 8: 20 hours |
|
* Functional vs non-functional testing
|
|
* Functional vs non-functional testing
|
|
|
|
|
|
|
|
|
|
**Storyboard**
|
|
Inspection methodology - deliverables, strategies/approach (not graded)<br>
|
|
<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.
|
|
|
|
|
|
|
|
2. 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.
|
|
|
|
|
|
|
|
3. 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.
|
|
|
|
|
|
|
|
4. 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.
|
|
|
|
|
|
|
|
5. 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.
|
|
|
|
|
|
|
|
6. As a customer, I want different language options so I can choose a language I’m most comfortable with.
|
|
|
|
|
|
|
|
7. 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.
|
|
|
|
|
|
|
|
8. 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.
|
|
|
|
<hr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Action Plan**<br>
|
|
|
|
|
|
|
|
*Fantastic 4*:<br>
|
|
|
|
All team members had participated in two scheduled weekly meetings plus two additional meetings during the break, discussing details about this milestone and product alpha due in two weeks after the break.<br>
|
|
|
|
Time spent as a team: 6、2 hours (1.5 hours per team meeting, 4 meetings in total)
|
|
|
|
|
|
|
|
Ali: <br>
|
|
|
|
Drawed the sequence diagram and activity diagram with the team.<br>
|
|
|
|
Will create a database of the system for the next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 2 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Jordan: <br>
|
|
|
|
Scheduled and booked a team meeting room as a regular weekly task.<br>
|
|
|
|
Drawed the sequence diagram and activity diagram with the team.<br>
|
|
|
|
Will work closely with Ali on connections in the database for the next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 2 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Nick: <br>
|
|
|
|
Worked on Preliminary Implementation (Hello World App) on the departmental Virtual Machine plus Readme file documentation.<br>
|
|
|
|
Will work closely with Ali on connections between HTML pages and database for next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 6 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours
|
|
|
|
|
|
|
|
Wes: <br>
|
|
|
|
Drafted up the sequence diagram, activity diagram and expanded UML diagram.<br>
|
|
|
|
Created Milestone 6 at Wiki and summarized Action Plan. <br>
|
|
|
|
Finished the final formatting of this milestone.<br>
|
|
|
|
Will work closely with Nick on connections between HTML pages and database for next two milestones.<br>
|
|
|
|
Individual time spent on Milestone 6: 5 hours<br>
|
|
|
|
Individual time will be spent on Milestone 7 & 8: 20 hours |
|
|
|
\ No newline at end of file |