The Release Candidate Test Plan
When all 3.16 17 tickets have been completed, we can begin testing, and we will follow the test plan detailed below.
...
If there are any blocker or critical bugs related to the features in the 3.16 17 release, they must be fixed and tested before the RC testing can begin;
If there are any open tickets related to the features in the 3.16 17 release, they must be completed and marked as Done before any RC testing begins;
Regular regression testing has been completed in previous sprints before we start the release candidate testing.
...
Test Phase | Components/Features | Assigned in Test Cycle | Dates | QA lead responsibilities |
|---|
RC 1 | Execution of the 3.16 17 RC1 test cases on Firefox (Regression testing concerning all components/features); Performance testing on Chrome; Exploratory and translation testing on Chrome.
| 3.16 17 RC1 | 3 full days (as needed) | Team Mind the Parrot: Aleksandra Hinc will provide the status of testing by the end of the day; Aleksandra Hinc will triage and prioritize any bugs found during RC testing; If there are blocker or critical bugs, they will be assigned to a 3.16RC1Bug17RC1Bug test cycle; Bugs are labeled 3.16RC1bug17RC1bug.
|
Bug triage | Bug triage for RC1 | Bug fixes test cycle for a given Release Candidate, e.g. 3.16 17 RC1 Bug fixes | 2 full days (as needed) | |
Suggested schedule, assuming we start testing on October 25April 15:
Week One:
Mon October 23April 08 | Tue October 24April 09 | Wed October 25April 10 | Thu October 26April 11 | Fri October 27April 12 |
|---|
| | | | | Start testing Testing is focused on regression testing (i.e. manual test case execution) and performance testing. Exploratory and translation testing is performed in the meantime, i.e. during the wait for the bug fixes or when someone doesn’t have any other testing to perform. Exploratory and translation testing has to be done instead of the code freeze tasks.
|
...
Week Two:
Mon April 15 | Tue April 16 | Wed April 17 | Thu April 18 | Fri April 19 |
|---|
| | | | |
Week Three:
Week Four:
Roles & Responsibilities
...
Members | Responsibilities | Questions |
|---|
Aleksandra Hinc David Crewe-Brown Artur Lebiedziński Daria Pionk Szymon Radziszewski Maciej Grochalski Krzysztof Pokrywka (Deactivated) | Review the list of bugs provided on the QA Slack channel; Prioritize bugs; Communicate which bugs need to be fixed; Aleksandra Hinc to create test cycles for retesting if needed; Aleksandra Hinc to provide the status update on the bug fixes on the QA Slack channel as needed; Aleksandra Hinc to communicate on Slack the bugs that have been added to the board for the day.
| When should we meet every day? Meetings will be held every two days (6am PST) and a communication on the bug triage status at the end of the day; Guidance on bug prioritization is located here: http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#reporting-bugs; If there are bugs, then testing for the RC will be done in UAT only; If there are critical/blocker bugs found, then we must retest. If the bugs concern the Reference Data service, all test cases related to the RC in which the bug was found have to be executed again. If the bug concerns any other service, only test cases concerning the service in which it was found have to be executed again; Communication of the test plan before we start testing for the release:
|
...