Quality Assurance Plan
Introduction
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.
Scope
Inspection methodology
Reference of FURPS+
-
FURPS:
- Functionality
- Usability
- Reliability
- Performance
- Supportability
-
The Plus +:
- Design constraints
- Implementation requirements
- Interface requirements
- Physical requirements
-
Functional:
All eight ranked user stories with eligible acceptance tests (from Milestone 5 ). -
Non-Functional:
The font size of text, webpage loading speed, etc.
Quality Objective
An easy-to-use web application for not just markers but everyone who has basic technology of computer
Roles and Responsibilities
Ali and Jordan:
All Back-End related testings of the codes they implemented: the database, Nodejs, Javascripts, etc.
Wes and Nick:
All Front-End related testing of the codes they implemented: the HTML pages with CSS stylings, shared responsibilities of testing of Nodejs, Javascripts, etc.
Wes:
Overall testing and Web Application Testing of the entire project.
Test methodology
- Deliverables:
- A fully-functioning system without bugs
- Testing approach:
- White-box testing
- Black-box testing
- Testing levels:
- Unit testing
- Integration testing
- System testing
- Operational acceptance testing
- Testing types:
- Installation testing
- Compatibility testing
- Regression testing
- Acceptance testing
- Alpha testing
- Beta testing
- Functional vs non-functional testing
- Test tools with bug repoarting:
- Brackets without debugger
- Visual Stduio with debuger
- Browsers: Chrom, Firefox, Edge, etc.
Inspection methodology
- Deliverables:
- A well-developed website ready to be used
- Inspection approach:
- Planning
- Overview meeting
- Preparation
- Inspection meeting
- Rework
- Follow-up
Action Plan
Fantastic 4:
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.
Time spent as a team: 1.5 hours (1 hour of Tuesday meeting, 0.5 hour of Thursday meeting, 1.5 hours in total)
Ali (Back-End):
Checked the Milestone 7 and fixed errors when necessary.
Will continue to create a well-developped database of the system with correct logics built for searching connection flights for the next milestone.
Individual time spent on Milestone 6: 1 hour
Individual time will be spent on Milestone 8: 15 hours
Jordan (Back-End):
Scheduled and booked a team meeting room as a regular weekly task.
Checked the Milestone 7 and fixed errors when necessary.
Will continue work closely with Ali on connections in the database for the next milestone.
Individual time spent on Milestone 6: 1 hour
Individual time will be spent on Milestone 8: 15 hours
Nick (Front-End):
Checked the Milestone 7 and fixed errors when necessary.
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.
Individual time spent on Milestone 6: 1 hour
Individual time will be spent on Milestone 8: 15 hours
Wes (Front-End):
Created and summarized Milestone 7 at Wiki.
Finished the final formatting of this milestone.
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.
Individual time spent on Milestone 6: 5 hours
Individual time will be spent on Milestone 8: 15 hours