Test Plan

1 Regression Test Plan
2 Release Candidate Test Plan
- 2.1 Please execute the test cases in the order that they are listed in the test cycle for the Release Candidate testing.
3 Roles & Responsibilities
- 3.1 QA Team Leads
- 3.2 Bug Triage team
- 3.3 Communication on the Test Plan and the daily testing status:
- 3.4 Environments and Demo Data for testing
- 3.5 Edge Case and Exploratory Testing scenarios
  - 3.5.1 Edge Case Testing examples:
  - 3.5.2 Performance Testing
4 Regression Testing Status
- 4.1 Phase 1 Bug Tracking:
- 4.2 Phase 2 Bug Tracking:
5 Release Candidate Testing Bugs
- 5.1 Release Candidate 1:
- 5.2 Release Candidate 2:
- 5.3 Release Candidate 3:

Regression Test Plan

During Sprint 49 we will follow the regression test plan detailed below:

If there are Blocker or Critical bugs when we start Sprint 49, they must be fixed and tested before Regression testing can begin
Regression Test Plan will only include Phase 1&2 (Two full days of testing for both teams, and 2 days for bug fixes and bug fix testing)
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 next phase
Testing will be done in test and uat environments

Test Phase	Components/Features	Assigned in Test Cycle	Dates	QA lead responsibilities

Test Phase	Components/Features	Assigned in Test Cycle	Dates	QA lead responsibilities
Phase 1	Requisitions External Fulfillment Stock Management CCE Administration	3.3 Regression Phase 1	1 full day Team Parrot 1 full day Team ILL	Team Parrot: @Joanna Bebak (Deactivated) Joanna will provide status of testing by end of day. Any test cases that are not completed by end of day will be picked up by Team ILL. After Team Parrot finishes testing this 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 Phase 1 Bug test cycle for Team Parrot to begin work the next day. Bugs are labeled Phase1bug Team ILL: @Sam Im (Deactivated) After Team ILL finishes testing, there should be no more remaining test cases. Sam will provide status of testing by end of day. Sam will triage and prioritize any bugs found in Phase 1 (all bugs reported by Team Parrot & Team ILL) If there are Blocker or Critical bugs they will be assigned to a Phase 1 Bug test cycle for Team Parrot to begin work the next day.
Bug triage	Bug triage for Phase 1	Phase 1 Bug test cycle	1 full day Team Parrot This bug test cycle is done in parallel (on the same day - as Phase 2 below)
Phase 2	Bug Fixes & edge cases Exploratory Testing Translations Performance Testing for: Regression New features	3.3 Regression Phase 2	1 full day Team Parrot 1 full day Team ILL	Anyone not participating in bug fixes will complete Edge case, exploratory or translation testing For all bug fixes, we will require re-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. Brandon and one other team member will complete performance testing Bugs are labeled Phase2bug
Bug triage	Bug triage for Phase 2	Phase 2 Bug test cycle	1 full day Team Parrot (as needed)

After these test phases are complete, and all tests have passed with no Blocker or Critical bugs, we can deploy the release candidate and begin the next phases of testing that are defined below.

Release Candidate Test Plan

Please execute the test cases in the order that they are listed in the test cycle for the Release Candidate testing.

Test Phase	Components/Features	Assigned in Test Cycle	Dates

Test Phase	Components/Features	Assigned in Test Cycle	Dates
Phase 1	Requisitions External Fulfillment Stock Management CCE Administration	3.3 RC Phase 1 (Any test cases that are not completed by end of day for Team Parrot will be picked up by Team ILL. @Sam Im (Deactivated) will assign the remaining test cases.)	1-2 days
Bug triage	Bug fix RC1	as needed
Phase 2	Local Fulfillment Vaccine stock based requisitions (Vaccine SBR) POD	3.3 RC Phase 2 (Any test cases that are not completed by end of day will be picked up by Team Parrot the next day. @Joanna Bebak (Deactivated) will assign the remaining test cases.)	1-2 days
Bug triage	Bug fix Phase 2	as needed
Phase 3	Bug Fixes & edge cases Exploratory Testing Translations Low bandwith - @Brandon Bowersox-Johnson will track	@Joanna Bebak (Deactivated) - Since the tests in this phase (exploratory or edge cases) are adhoc or do not exist, how should we track the test cases that are executed? Or test steps so that someone can reproduce the tests? A bug fix test cycle will be created as needed	2 days

Roles & Responsibilities

QA Team Leads

Sam and Joanna will be the QA leads for each team.

Owner	Responsibilities	Questions

Owner

Responsibilities

Questions

@Sam Im (Deactivated) (for Team ILL)

@Joanna Bebak (Deactivated) (for Team Parrot)

Create Test Cycles
Create missing test cases and assign to test cycles
Assign Test Cases to team members
Point person for any questions about test cases from the team
Review execution of the test cycles, there should be positive progress during the day
Prioritize bugs per test cycle, Check that developers have detailed proposed solutions (if time allows or developer's experience allows) When a bug is created during the day, the bugs are triaged before end of day and detailed in the daily QA slack communication
Report the status of each test cycle, including defects reported, before end of day
After a bug fix test cycle, review automated testing and provide status before end of day (go to http://build.openlmis.org/view/all/builds)

Team ILL & Team Parrot

Execute test cases assigned to you
Record the test execution by following these steps:Testing Process & Test Plans#ExecutingTestCase
Enter Defects as encountered:
- If there are any Blocker bugs, try to spend time completing a root cause analysis and add details in the bug ticket for ease in bug triage
- When a defect is found, research and provide proposals in the ticket for review by Sam & Joanna (as time allows)
- All bugs are labeled with their release candidate: RC1, RC2, etc.
Assist other testers as needed
@Brandon Bowersox-Johnson or @Chongsun Ahn (Unlicensed) (who else can do this since Josh is out?) to set up update environment(s) with Release Candidate before testing begins
@Brandon Bowersox-Johnson to provide updates on automated performance testing results
@Brandon Bowersox-Johnson to coordinate manual UI Performance Testing

@Brandon Bowersox-Johnson will work with @Paweł Gesek on assigning responsibility for member on Team Parrot to help test UI performance during the release candidate testing
@Sam Im (Deactivated) & @Joanna Bebak (Deactivated) will create a bug test cycle when bugs are found, and assign the test cases to them, for each phase there will be a separate bug fix test cycle