The purpose of this page is to outline the test plan for the 3.3.1 patch release that will also inform future patch release processes.
Testing Overview
- Test bug fixes included in the patch release.
- Regression test components that are impacted by the bug fix.
- Ongoing development by other team members should not be impacted.
- Any blocker or critical bugs related to patch release testing will be reviewed in a go/no-go meeting, if there are blocker or critical bugs, we should not release the patch.
- 1-3 days of testing for the patch release process, 1-2 team members testing
Test Plan
Test environment: Perftest? Perftest and UAT? How do we make sure we don't impact active sprint testing for performance?
Action Items:
- May need to create a ticket to automatically deploy to a new environment (patch release)
- Demo-v3 (who is using this?) This is running the latest release. We might be able to use this to test the patch release. Maybe we can say that it is down for 1-2 days.
- There is a possibility that performance may change, and we should test as part of the patch release.
- Load Malawi dataset
- Load Patch Release to perftest
- 2-4 hours
- Can be done in parallel with manual regression testing
Bug fix: OLMIS-4728 - Getting issue details... STATUS
Test case: OLMIS-4311 - Getting issue details... STATUS
Regression Test cases:
- Regression testing should be done in uat (or other environment to make sure we don't impact active sprint testing?)