When all 3.8 tickets have been completed, we can begin testing, and we will follow the test plan detailed below.
Before we start the Release Candidate testing:
Starting the Release Candidate testing:
Test Phase | Components/Features | Assigned in Test Cycle | Dates | QA lead responsibilities |
---|---|---|---|---|
RC 1 |
| 3 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.8 RC1 Bug fixes | 3 full days (as needed) |
|
Suggested schedule, assuming we start testing on December 5:
Week One:
Thu Dec 05 | Fri Dec 06 | Mon Dec 09 | Tue Dec 10 | Wed Dec 11 |
---|---|---|---|---|
|
|
|
|
|
Week Two:
Thu Dec 12 | Fri Dec 13 | Mon Dec 16 | Tue Dec 17 | Wed Dec 18 |
---|---|---|---|---|
|
|
|
|
|
Week Three:
Thu Dec 19 | Fri Dec 20 | Mon Dec 23 | Tue Dec 24 | Wed Dec 25 |
---|---|---|---|---|
Week Four:
Thu Dec 26 | Fri Dec 27 | Mon Dec 30 | Tue Dec 31 | Wed Jan 01 |
---|---|---|---|---|
Joanna Bebak (Deactivated) will be the QA lead for the Mind the Parrot team.
Owner | Responsibilities | Questions/Tasks before release begins |
---|---|---|
| ||
Team leads: |
|
|
Team responsibilities |
|
|
Members | Responsibilities | Questions |
---|---|---|
|
|
Environments: uat.openlmis.org.
Refer to the demo data readme for more details about user permissions: https://github.com/OpenLMIS/openlmis-referencedata/blob/master/src/main/resources/db/demo-data/README.md.
ONLY test with the users "admin" or "administrator" when executing test cases related to administrative activities.
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 | reporter1 reporter2 reporter3 | All programs |
The following Superset reports need to be tested:
Each report is covered by one manual test case. Only one person should be executing a test case concerning the Superset reports at a time. They should inform others on the QA Slack channel that they have just started executing the test case, that they re-started the processor groups in NiFi, and that they finished executing the test case. Then, some other person can start executing another test case related to the Superset reports.
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.
The performance testing scenarios are located here: Performance Metrics.
Enter the performance metrics here: https://docs.google.com/spreadsheets/d/1z1D4EUHsE-R_bUTt4HYcWiVDEy_UX50lZhdiyiC4bYg/edit#gid=0.
Deploying the release: Release Checklist 3.4.