Versions Compared

Old Version 17

changes.mady.by.user Sam Im (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Sam Im (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


...

titleTest Plan Work in Progress

...


Release Candidate Test Plan

...


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)version 

3.5 RC1 Test cycle




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 triageBug 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

3.5 RC2 test cycle




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 triageBug triage for Phase 2

Phase 2 Bug test cycle

Phase 2 bug fix cycle

1 full day  (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.

...

Suggested Schedule: Assuming we start testing on Nov 22nd (Actual testing start date was Nov 30)

Week One:

Mon Nov 19Tues Nov 20Wed Nov 21Thurs Nov 22Fri Nov 23
  • Sent Malawi notification that we expect to start testing on Thurs

End of Sprint 112

  • Overview of 3.5 test plan/schedule in the Product Committee meeting

Sprint 112 Showcase

Go/No-go decision to start 3.5 release testing

Teams worked on finishing 3.5 features until Nov 30



Week Two:

Mon Nov 26Tues Nov 27Wed Nov 28Thurs Nov 29Fri Nov 30




Teams worked on finishing 3.5 features until Nov 30

Start testing

Testing is focused on testing the new features in Phase 1 of testing, then regression testing in Phase 2

Bug Triage - if needed

Continue testing


Week TwoWeek Three:

Mon
Nov 26
Dec 3Tues
Nov 27
Dec 4Wed
Nov 28
Dec 5Thurs
Nov 29
Dec 6Fri
Nov 30
Dec 7

Daily bug triage at 6am PST

Begin Phase 2 testing if no bugs found

If bugs found, Phase1bug fix
  • Deployed 3.5 RC to Malawi to begin testing
Daily bug triage at 6am PST

Continue testing 

Daily bug triage at 6am PST

Bug fix as needed

If bugs found, Phase2bug fix

Daily bug triage at 6am PSTDaily bug triage at 6am PST


Week

...

Four:

Mon Dec
3
10Tues Dec
4
12Wed Dec
5
13Thurs Dec
6
14Fri Dec
7
15
Daily bug triage at 6am PSTDaily bug triage at 6am PST

Daily bug triage at 6am PST

  • No bugs found 
  • All testing completed
  • Release deployed



Gliffy
imageAttachmentIdatt414482475
baseUrlhttps://openlmis.atlassian.net/wiki
migration1
nameRelease Candidate Test Plan
diagramAttachmentIdatt414449672
containerId400818373
timestamp1531230764065

...