2019-03-25 QA Weekly Meeting notes

25min

Process & status reporting

• Testing status & automating reporting for each sprint

  • 3.6 test status and reporting

  • Bug triage reporting page

  • Other reports?

• 3.6 Test Plan (@Joanna Bebak (Deactivated) )

  • 3.6 release testing is scheduled to start in Sprint 123

  • Other schedule questions:

    • If we can start early, what testing should we start with? If there are delays to start, how do we handle them, for example if the reporting work isn’t done yet, can we start?

  • Environment setup - need to inform Josh when we are ready to set up the environment for release testing (create a ticket and assign to him)

  • Team responsibilities and owners

    • Need to confirm who will be responsible and available for day to day and bug triage

  • Demo data review for new features (any new users or facilities to add to demo data on Test Plan page? Should we include devs in this review?)

  • Demo data bugs that should be cleaned up before we start testing 3.6 https://openlmis.atlassian.net/issues/?filter=20642

• Any other topics to add? @Joanna Bebak (Deactivated) @Joanna Szymańska (Deactivated)

Next steps for 3.6 test plan:

@Joanna Bebak (Deactivated) & @Sam Im (Deactivated) will determine when to schedule the test plan review.

Tickets that have been open and have not changed status @Wesley Brown :

https://openlmis.atlassian.net/browse/OLMIS-5438 - is still in QA

Bugs that have been in Roadmap status for over a year @Wesley Brown :

https://openlmis.atlassian.net/browse/OLMIS-4412

https://openlmis.atlassian.net/browse/OLMIS-4556We need to decide what to do with these bugs but it is a low priority.