|
|
***Quality Assurance Plan**<br>*
|
|
|
|
|
|
**Introduction**<br>
|
|
|
Our team is developing a website for a flight reservation system, therefore we will be combining the conventional testing strategies of software and the innovated Web Application Testing.<br>
|
|
|
Our team is developing a website for a flight reservation system; therefore we will be combining the conventional testing strategies of software and the innovated Web Application Testing.<br>
|
|
|
|
|
|
**Scope**<br>
|
|
|
**Inspection methodology**<br>
|
... | ... | @@ -31,7 +31,7 @@ An easy-to-use web application for not just markers but everyone who has basic t |
|
|
Ali and Jordan:<br>
|
|
|
All Back-End related testings of the codes they implemented: the database, Nodejs, Javascripts, etc.<br>
|
|
|
Wes and Nick:<br>
|
|
|
All Front-End related testing of the codes they implemented: the HTML pages with CSS stylings, shared responsibilities of testing of Nodejs, Javascripts, etc.<br>
|
|
|
All Front-End relevant testing of the systems they implemented: the HTML pages with CSS stylings, shared responsibilities of testing of Nodejs, Javascripts, etc.<br>
|
|
|
Wes:<br>
|
|
|
Overall testing and Web Application Testing of the entire project.<br>
|
|
|
|
... | ... | @@ -72,31 +72,31 @@ Overall testing and Web Application Testing of the entire project.<br> |
|
|
|
|
|
**Action Plan**<br>
|
|
|
*Fantastic 4*:<br>
|
|
|
All team members had actively participated in two scheduled weekly meetings discussing details about this milestone, these two meeting was short due to the nature of this milestone. <br>
|
|
|
Time spent as a team: 1.5 hours (1 hour of Tuesday meeting, 0.5 hour of Thursday meeting, 1.5 hours in total)
|
|
|
All team members had actively participated in two scheduled weekly meetings discussing details about this milestone; these two meeting was short due to the nature of this milestone. <br>
|
|
|
Time spent as a team: 1.5 hours (1 hour of Tuesday meeting, 0.5 hours of Thursday meeting, 1.5 hours in total)
|
|
|
|
|
|
Ali (Back-End): <br>
|
|
|
Checked the Milestone 7 and fixed errors when necessary. <br>
|
|
|
Will continue to create a well-developped database of the system with correct logics built for searching connection flights for the next milestone.<br>
|
|
|
Individual time spent on Milestone 6: 1 hour<br>
|
|
|
Will continue to create a well-developed database of the system with correct logics built for searching connection flights for the next milestone.<br>
|
|
|
Individual time spent on Milestone 7: 1 hour<br>
|
|
|
Individual time will be spent on Milestone 8: 15 hours
|
|
|
|
|
|
Jordan (Back-End): <br>
|
|
|
Scheduled and booked a team meeting room as a regular weekly task.<br>
|
|
|
Checked the Milestone 7 and fixed errors when necessary. <br>
|
|
|
Will continue work closely with Ali on connections in the database for the next milestone.<br>
|
|
|
Individual time spent on Milestone 6: 1 hour<br>
|
|
|
Individual time spent on Milestone 7: 1 hour<br>
|
|
|
Individual time will be spent on Milestone 8: 15 hours
|
|
|
|
|
|
Nick (Front-End): <br>
|
|
|
Checked the Milestone 7 and fixed errors when necessary. <br>
|
|
|
Will work closely with Wes on the creation of HTML pages with CSS styling and the connection between the database and HTML pages for next milestone.<br>
|
|
|
Individual time spent on Milestone 6: 1 hour<br>
|
|
|
Individual time spent on Milestone 7: 1 hour<br>
|
|
|
Individual time will be spent on Milestone 8: 15 hours
|
|
|
|
|
|
Wes (Front-End): <br>
|
|
|
Created and summarized Milestone 7 at Wiki. <br>
|
|
|
Finished the final formatting of this milestone.<br>
|
|
|
Will work closely with Nick on the creation of HTML pages with CSS styling and the connection between the database and HTML pages for next milestone.<br>
|
|
|
Individual time spent on Milestone 6: 5 hours<br>
|
|
|
Individual time spent on Milestone 7: 5 hours<br>
|
|
|
Individual time will be spent on Milestone 8: 15 hours |
|
|
\ No newline at end of file |