Update Final Submission authored by Jorgen Wiebe (jow172)'s avatar Jorgen Wiebe (jow172)
......@@ -95,16 +95,14 @@ Epic 5: As MaryShopaholic, I would like to see my spending visually in a way tha
## Quality Assurance Plan (testing, inspection, acceptance)
Introduction
#### Introduction
* Automated and Regression testing
* User testing
* Experienced users
* Inexperienced users
Scope
#### Scope
......@@ -140,7 +138,7 @@ Scope
* System should be easily extendable and modular
* System should run on MacOS, Windows, and Linux
Quality Objective -
#### Quality Objective -
......@@ -148,7 +146,7 @@ Quality Objective -
* Users are able to use it with little guidance
* UI is visually appealing
Roles and responsibilities of team members
### Roles and responsibilities of team members
......@@ -166,9 +164,7 @@ Roles and responsibilities of team members
* Testing receipt input
* Testing searching
Test methodology
### Test methodology
* Deliverables
* Test Scripts
......@@ -182,7 +178,7 @@ Test methodology
* Test tools
* None
Inspection methodology - deliverables, strategies/approach
### Inspection methodology - deliverables, strategies/approach
......@@ -193,9 +189,7 @@ Inspection methodology - deliverables, strategies/approach
* Pair programming
* Code review
Acceptance test methodology
### Acceptance test methodology
* Deliverables
* Acceptance tests for all implemented user stories
......@@ -204,7 +198,6 @@ Acceptance test methodology
### Code Inspection Criteria
1. Completeness(of reflection by code of requirements)
1. Each such method has appropriate parameters
2. Consistency (of layout, name choice, and code organization)
......
......