The 3.10 Regression and Release Candidate Test Plan

The Release Candidate Test Plan

When all 3.10 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 when we start Sprint 156, 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.10 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 (Three full days of testing, and 3 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.

Suggested schedule, assuming we start testing on September 24:

Week One:

Week Two:

Week Three:

Week Four:

Roles & Responsibilities

QA Team Leads

Joanna Szymańska (Deactivated) will be the QA lead for the Mind the Parrot team.

The Bug Triage team

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;
  • Joanna Szymańska (Deactivated) will post any test cases or items that need attention and review by the end of her day on the QA Slack channel;
  • Joanna Szymańska (Deactivated) 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.

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.

Test Data

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.

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.