The 3.14 Regression and Release Candidate Test Plan

The Release Candidate Test Plan

When all 3.14 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 related to the features in the 3.14 release, 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.14 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.