The 3.12 Regression and Release Candidate Test Plan

The Release Candidate Test Plan

When all 3.12 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 182, 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.12 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:



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

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)

  • @Szymon Rujner

     to lead the Bug Triage meetings.

Suggested schedule, assuming we start testing on October 13:

Week One:

Mon Oct 11

Tue Oct 12

Wed Oct 13

Thu Oct 14

Fri Oct 15

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

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

Week Three:

Mon Oct 25

Tue Oct 26

Wed Oct 27

Thu Oct 28

Fri Oct 29

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

Mon Nov 01

Tue Nov 02

Wed Nov 03

Thu Nov 04

Fri Nov 05



 



 



Roles & Responsibilities

QA Team Leads

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

Owner