Page Comparison

The Release Candidate Test Plan

...

Mon September 26

Tue September 27

Wed September 28

Thu September 29

Fri September 30

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.

...

Mon October 03	Tue October 04	Wed October 05	Thu October 06	Fri October 07
Daily bug triage at 3PM CEST		Daily bug triage at 3PM CEST	The 3.14 Release	Daily bug triage at 3PM CEST

...

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;
Szymon Rujner
to create test cycles for retesting if needed;
Szymon Rujner
to provide the status update on the bug fixes on the QA Slack channel as needed;
Szymon Rujner
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:
- Szymon Rujner
  is responsible for communicating this test plan on the QA Slack channel.

...