Page Comparison

The Release Candidate Test Plan

...

Mon April 01	Tue April 02	Wed April 03	Thu April 04	Fri April 05
		Deploy 3.17 RC 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.	Testing	Testing

Week Two:

Mon April 08
Testing

Week Three:

Week Four:

...

Members

Responsibilities

Questions

Review the list of bugs provided on the QA Slack channel;
- Only bugs that have been entered and labeled RC1bug will be reviewed during the triage;
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:
- Aleksandra Hinc
  is responsible for communicating this test plan on the QA Slack channel.

...