...
...
...
...
The Release Candidate Test Plan
When all 3.12 13 tickets have been completed, we can begin testing, and we will follow the test plan detailed below.
...
If there are any blocker or critical bugs when we start Sprint 182194, 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 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.
...
Test Phase | Components/Features | Assigned in Test Cycle | Dates | QA lead responsibilities |
---|---|---|---|---|
RC 1 |
| 3.12 13 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.12 13 RC1 Bug fixes | 3 full days (as needed) |
|
Suggested schedule, assuming we start testing on October 13March 17:
Week One:
Mon Oct 11March 14 | Tue Oct 12March 15 | Wed Oct 13March 16 | Thu Oct 14March 17 | Fri Oct 15March 18 |
---|---|---|---|---|
|
|
Week Two:
Mon Oct 18March 19 | Tue Oct 19March 20 | Wed Oct 20March 21 | Thu Oct 21March 22 | Fri Oct 22March 23 |
---|---|---|---|---|
|
|
|
Week Three:
Mon Oct 25March 24 | Tue Oct 26March 25 | Wed Oct 27March 26 | Thu Oct 28March 27 | Fri Oct 29March 28 |
---|---|---|---|---|
|
|
|
Week Four:
Mon Nov Apr 01 | Tue Nov Apr 02 | Wed Nov Apr 03 | Thu Nov Apr 04 | Fri Nov Apr 05 |
---|---|---|---|---|
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 |
---|---|---|
| ||
Team leads: |
|
|
Team responsibilities |
|
|
The Bug Triage team
Members | Responsibilities | Questions |
---|---|---|
Dominika Bieńkowska (Deactivated)Krzysztof Pasiek (Deactivated) Hubert (Deactivated)Magdalena Toczek (Deactivated) |
|
|
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;
will post any test cases or items that need attention and review by the end of her day on the QA Slack channel;
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.
...
ONLY test with the users "admin" or "administrator" when executing test cases related to administrative activities.
Test Data
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 |
|
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.
...