The 3.15 Regression and Release Candidate Test Plan

RC 1

• Execution of the 3.15 RC1 test cases on Firefox (Regression testing concerning all components/features);

• Performance testing on Chrome;

• Exploratory and translation testing on Chrome.

3.15 RC1

4 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.15RC1Bug test cycle;

• Bugs are labeled 3.15RC1bug.

Bug triage

Bug triage for RC1

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

2 full days (as needed)

• @Aleksandra Hinc

   to lead the Bug Triage meetings.

• Deploy 3.15 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.

• Daily bug triage at 3PM CEST

Daily bug triage at 11:30 AM CEST

@Aleksandra Hinc

• 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 @Aleksandra Hinc  (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.

• @Aleksandra Hinc

   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.

@Aleksandra Hinc

@David Crewe-Brown

@Artur Lebiedziński

@Nikola Laskowska (Deactivated)

@Daria Pionk

@Adam Nawrot (Deactivated)

@Szymon Radziszewski (Deactivated)

• 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.

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