The 3.18 Regression and Release Candidate Test Plan
The Release Candidate Test Plan
When all 3.18 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 related to the features in the 3.18 release, 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.18 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 (Five full days of testing, and 1 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 |
---|---|---|---|---|
RC 1 |
| 3.18 RC1 | 5 full days (as needed) | Team Mind the Parrot:
|
Bug triage | Bug triage for RC1 | Bug fixes test cycle for a given Release Candidate, e.g. 3.18 RC1 Bug fixes | 2 full days (as needed) |
|
Suggested schedule, assuming we start testing on October 23:
Week One:
Mon October 21 | Tue October 22 | Wed October 23 | Thu October 24 | Fri October 25 |
---|---|---|---|---|
|
|
|
|
|
Week Two:
Mon October 28 | Tue October 29 | Wed October 30 | Thu October 31 | Fri November 1 |
---|---|---|---|---|
|
|
|
|
|
Week Three:
|
|
|
|
|
---|---|---|---|---|
|
|
|
|
|
Week Four:
|
|
|
|
|
---|---|---|---|---|
|
|
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 |
---|---|---|
@Szymon Rujner |
| |
Team leads: |
|
|
Team responsibilities |
|
|
The Bug Triage team
Members | Responsibilities | Questions |
---|---|---|
@Szymon Rujner @Artur Lebiedziński @Maciej Grochalski
|
|