The 3.13 Regression and Release Candidate Test Plan

The Release Candidate Test Plan

When all 3.13 tickets have been completed, we can begin testing, and we will follow the test plan detailed below.

Before we start the Release Candidate testing:

If there are any blocker or critical bugs when we start Sprint 194, 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.13 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.

Starting the Release Candidate testing:

If there are no open blocker or critical bugs, then move to the release candidate's deployment and testing:
- RC1 (Three full days of testing, and 3 days for bug fixes and bug fix testing) for each release candidate as needed;
- The testing will be done in the following environments:
  - Team Mind the Parrot's UAT environment: https://uat.openlmis.org;
  - Performance testing: https://perftest.openlmis.org.
How to enter bugs: Testing Process & Test Plans#EnterDefectsduringsprinttesting;
Prioritization of bugs: http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#reporting-bugs.

Test Phase	Components/Features	Assigned in Test Cycle	Dates	QA lead responsibilities

Test Phase

Components/Features

Assigned in Test Cycle

Dates

QA lead responsibilities

RC 1

Execution of the 3.13 RC1 test cases on Firefox (Regression testing concerning all components/features);
Performance testing on Chrome;
Exploratory and translation testing on Chrome.

3.13 RC1

5 full days (as needed)

Team Mind the Parrot:

@Szymon Rujner
will provide the status of testing by the end of the day;
@Szymon Rujner
will triage and prioritize any bugs found during RC testing;
If there are blocker or critical bugs, they will be assigned to a 3.13RC1Bug test cycle;
Bugs are labeled 3.13RC1bug.

Bug triage

Bug triage for RC1

Bug fixes test cycle for a given Release Candidate, e.g. 3.13 RC1 Bug fixes

3 full days (as needed)

@Szymon Rujner
to lead the Bug Triage meetings.

Suggested schedule, assuming we start testing on March 17:

Week One:

Mon March 14	Tue March 15	Wed March 16	Thu March 17	Fri March 18

Mon March 14

Tue March 15

Wed March 16

Thu March 17

Fri March 18

Deploy 3.13 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.

Week Two:

Mon March 21	Tue March 22	Wed March 23	Thu March 24	Fri March 25

Mon March 21	Tue March 22	Wed March 23	Thu March 24	Fri March 25
Daily bug triage at 3PM CEST		Daily bug triage at 3PM CEST		Daily bug triage at 3PM CEST

Week Three:

Mon March 28	Tue March 29	Wed March 30	Thu March 31	Fri Apr 01

Mon March 28	Tue March 29	Wed March 30	Thu March 31	Fri Apr 01
Daily bug triage at 3PM CEST		Daily bug triage at 3PM CEST	The 3.13 Release

Week Four:

Mon Apr 04	Tue Apr 05	Wed Apr 06	Thu Apr 07	Fri Apr 08

Mon Apr 04	Tue Apr 05	Wed Apr 06	Thu Apr 07	Fri Apr 08

Roles & Responsibilities

QA Team Leads

@Szymon Rujner will be the QA lead for the Mind the Parrot team.

Owner	Responsibilities	Questions/Tasks before release begins

Owner

Responsibilities

Questions/Tasks before release begins

@Szymon Rujner

Create test cycles;
Create missing test cases and assign them to test cycles;
Point person for any questions about test cases from the team;
Review execution of the test cycles, there should be progress during the day, and communicate the status at the end of the day;
Triage bugs before the scheduled bug triage;
Prioritize bugs per test cycle, check that developers have detailed proposed solutions (if time or the developer's experience allows). When a bug is created during the day, the bugs are triaged before the end of the day and detailed in the daily QA Slack communication;
Report the status of each test cycle, including defects reported, before the end of day;
After a bug fix test cycle, review automated testing and provide its status before the end of the day (go to http://build.openlmis.org/view/all/builds).

Team leads:

Attend and make a decision for Go/No-Go before we start the release process:
- Agree all features are done and ready to be tested;
- The team is ready to start testing;
- Review roles & responsibilities.
Coordinate manual testing with team members;
Coordinate manual performance testing with team members;
Assign bugs to developers after they have been prioritized at the bug triage;
Refresh test environments as needed (see the instructions here: /wiki/spaces/OP/pages/112106340).

Team Mind the Parrot focuses on manual performance testing;
Team Mind the Parrot typically refreshes all test environments during the release testing.

Team responsibilities

Execute the test cases assigned to you;
Record the test execution by following these steps: Testing Process & Test Plans#ExecutingTestCase;
Enter bugs as encountered:
- If there are any blocker bugs, try to spend some time completing a root cause analysis and add the details in the bug ticket for ease at the bug triage;
- When a bug is found, research and provide proposals in the ticket for review by @Szymon Rujner (as time allows);
- Check the bugs for completeness, proposed solutions, priorities and labels;
- All bugs are labeled with their release candidate: RC1, RC2, etc.
Assist other testers as needed.

@Szymon Rujner
will create a bug test cycle when bugs are found, and assign the test cases to them. For each RC, there will be a separate bug fix test cycle.

The Bug Triage team

Members	Responsibilities	Questions

Members

Responsibilities

Questions

@Szymon Rujner

@Wesley Brown

@Nikola Laskowska (Deactivated)

@Dominika Bieńkowska (Deactivated)

@Hubert (Deactivated)

@Trevor Lambiotte
@David Crewe-Brown

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.

Communication on the Test Plan and the daily testing status:

What needs to be communicated daily?
- The test cycle execution status (including the test cycle's name and % of completion);
- # of test cases that were executed, passed and failed;
- @Szymon Rujner
  will post any test cases or items that need attention and review by the end of her day on the QA Slack channel;
- @Szymon Rujner
  will communicate with the Malawi team (via the Malawi Slack channel) and notify them about the release candidate testing:
  - The communication of the scheduled start date before the release candidate testing begins;
  - The communication of when we start the release candidate testing (Malawi has one week to test);
  - The Malawi team is included in the daily bug triage meetings.
The best time of day (for each team to communicate the morning status and the end of day status & share blockers):
- The beginning of the day: Post what we are doing today;
- The end of day: Post the status of what we have done, and anything pending.

Environments and the demo data for testing

Environments: uat.openlmis.org.

Refer to the demo data readme for more details about user permissions: https://github.com/OpenLMIS/openlmis-referencedata/blob/master/src/main/resources/db/demo-data/README.md .

ONLY test with the users "admin" or "administrator" when executing test cases related to administrative activities.

Test Data

Component	Username	Program	Concerns

Component	Username	Program	Concerns
Requisition	srmanager1, smanager1, psupervisor, wclerk1 srmanager2, smanager2, psupervisor, wclerk1 srmanager4 (for the second approval), smanager4, dsrmanager, psupervisor chaz (for the second approval) administrator (testing requisition template updates/changes or program settings changes)	Family Planning Essential Meds ARV Essential Meds and Family Planning ARV Family Planning Essential Meds EPI ARV	Demo data restriction: May need to refresh the environment if all current requisition periods are processed (request and post the status on the QA Slack channel).
Stock Management	srmanager2 divo1, rivo	Family Planning, Essential Meds EPI
Fulfillment	vsrmanager1 vsrmanager2 divo1 divo2 rivo vwclerk1 wclerk1	EPI ARV
Administration (Reference Data)	admin administrator	All programs
CCE	divo1 divo2 vsrmanager1 (supervises Cuamba) vsrmanager2 (one facility)	EPI
Reporting	administrator	All programs

Exploratory Tests

Translations;
Edge case scenarios.

More details concerning this kind of testing can be found in the section on exploratory testing in the Testing Guide: https://openlmis.readthedocs.io/en/latest/conventions/testing.html#exploratory-testing.

Performance Tests

The performance testing scenarios are located here: Performance Metrics.

Enter the performance metrics here: Performance Metrics .

Deploying the release: Release Checklist 3.4.

OpenLMIS