Suggested schedule, assuming we start testing on December 5:
Thu Dec 05
Fri Dec 06
Mon Dec 09
Tue Dec 10
Wed Dec 11
Deploy 3.8 RC to Malawi and all other environments
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.
Create missing test cases and assign them to test cycles;
Point person for any questions about test cases from the team (from the QA and from the dev team);
Review execution of the test cycles, there should be progress during the day, and communicate the status at the end of the day;
Triage bugs before the scheduled bug triage;
Prioritize bugs per test cycle, check that developers have detailed proposed solutions (if time or the developer's experience allows). When a bug is created during the day, the bugs are triaged before the end of the day and detailed in the daily QA Slack communication;
Report the status of each test cycle, including defects reported, before the end of day;
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:
ONLY test with the users "admin" or "administrator" when executing test cases related to administrative activities.
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)
Essential Meds and Family Planning
Demo data restriction: May need to refresh the environment if all current requisition periods are processed (request and post the status on the QA Slack channel).
Family Planning, Essential Meds
Administration (Reference Data)
vsrmanager1 (supervises Cuamba)
vsrmanager2 (one facility)
The following Superset reports need to be tested:
Reporting Rate and Timeliness;
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.