The purpose of this is to get a set of quality-related tasks agreed with the development team that need to be completed before going to production
| Area | Tasks | Owner | Priority | Status |
|---|---|---|---|---|
| Functional | Definition of P1 cases for Milestone 1 This task is about having a list of P1 cases for the milestone 1 of essentials, so we can be sure all of them have been properly tested | MUST |
| |
| Functional | Testing of all P1 cases This task is about getting sure all P1 cases have been tested before releasing Milestone 1 of Essentials, how they are tested is not as important at this point but just ensure that they are tested, this task will be updated to reflect the testing of each P1 case here | MUST |
| |
| Functional | Bug bash session to check P1 cases | MUST |
| |
| Functional | DogFooding This task is about getting a running instance of the essentials client/server system and use it on a daily basis before launch to try to catch problems not detected in the previous phases | TBD | GOOD TO HAVE |
|
| Performance | Definition of minimum performance requirements for the milestone 1 of essentials client/server setup | TBD | GOOD TO HAVE |
|
| Performance | Testing of the system to be sure that it meets the acceptance criteria provided by
| TBD | GOOD TO HAVE |
|
| Automation | Code coverage report for P1 cases: For each P1 case defined in
| TBD | GOOD TO HAVE |
|
| Rollout plan | We need a definition of a rollout plan for the system that has to include at least:
| TBD | GOOD TO HAVE |
|