Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Release Candidate Test Plan


Test Phase


Assigned in Test Cycle


QA lead responsibilities

RC 1

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

  • Performance testing on Chrome;

  • Exploratory and translation testing on Chrome.

3.12 RC1

3 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.12RC1Bug test cycle;

  • Bugs are labeled 3.12RC1bug.

Bug triage

Bug triage for RC1

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

3 full days (as needed)


Mon Oct 11

Tue Oct 12

Wed Oct 13

Thu Oct 14

Fri Oct 15

  • Deploy 3.12 RC to Malawi and all other environments

  • 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 Oct 18

Tue Oct 19

Wed Oct 20

Thu Oct 21

Fri Oct 22

  • Daily bug triage at 3PM CEST

  • Daily bug triage at 3PM CEST

  • Daily bug triage at 3PM CEST


Mon Oct 25

Tue Oct 26

Wed Oct 27

Thu Oct 28

Fri Oct 29

  • Daily bug triage at 3PM CEST

  • Daily bug triage at 3PM CEST

  • Daily bug triage at 3PM CEST

  • The 3.12 Release

Week Four:

Mon Nov 01

Tue Nov 02

Wed Nov 03

Thu Nov 04

Fri Nov 05





Szymon Rujner

Paweł Muchowski (Deactivated) Wesley Brown

Nikola Laskowska

Dominika Bieńkowska (Deactivated)

Krzysztof Pasiek (Deactivated)

Hubert (Deactivated)

Magdalena Toczek (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;

  • 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:;

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