Page Comparison

Note

title	Test Plan Work in Progress

This test plan is being updated to support release candidate testing in Sprint 113.

...

Please execute the test cases in the order that they are listed in the test cycle, as assigned to you by the QA lead
If no Blocker or Critical bugs, then move to the release candidate deployment and testing
- RC Phase 1&2 (Two full days of testing for all teams, and 2 days for bug fixes and bug fix testing) for each release candidate as needed
- Testing will be done in test and uat environments (Sam Im (Deactivated) add links to new environments here)
  - Team Fast Parrot environment: TBD: https://uat3.openlmis.org
  - Team JSI environment: TBD https://uat4.openlmis.org
  - Team Mind the Gap environment: TBD https://uat.openlmis.org
  - Team Ona environment: TBD:https://uat4.openlmis.org
  - Performance testing (data set and environment set up)
How to enter bugs:Testing Process & Test Plans#EnterDefectsduringsprinttesting
Prioritization of bugs:http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#reporting-bugs

Test Phase	Components/Features	Assigned in Test Cycle	Dates	QA lead responsibilities
Phase 1	New features for 3.5 release Reporting: https://docs.google.com/document/d/1pVlgGXV9nb-nYlrTCRHS7Sor8ZrcnL59ch_Lnn2whZ0/edit	New features test cases will have 3.5 fix version (Joanna Bebak (Deactivated) Joanna Szymańska (Deactivated) to update)	1 full day each team	Team Fast Parrot: Joanna will provide status of testing by end of day. Joanna will triage and prioritize any bugs found in Phase 1 If there are Blocker or Critical bugs they will be assigned to a 3.5Phase1Bug test cycle Bugs are labeled 3.5Phase1bug Team Mind the Gap: Sam Im (Deactivated) Sam will provide status of testing by end of day. Sam will triage and prioritize any bugs found in Phase 1 Team JSI: Team Ona Gap:
Bug triage	Bug triage for Phase 1	Phase 1 Bug test cycle	1 full day This bug test cycle is done in parallel (on the same day - as Phase 2 below)
Phase 2	Regression Exploratory Testing Translations Performance Testing	3.5 RC2	1 full day each team	Anyone not participating in bug fixes will complete Edge case, exploratory or translation testing For all bug fixes, we will require pre-push reviews via pull requests or have more reviewers for any change. If reviews are still pending at the end of the day, please mention the reviewer in slack. Mateusz Kwiatkowski will lead performance testing Bugs are labeled 3.5Phase2bug
Bug triage	Bug triage for Phase 2	Phase 2 Bug test cycle	1 full day (as needed)

...

Versions Compared