2019-03-11 QA Weekly Meeting notes

25min

Process & status reporting

• Testing status & automating reporting for each sprint

  • OpenLMIS Test stats for all teams dashboard

  • Need to add test stats to the dashboard (maybe we could get some help from Sebastian?) to show resolution vs creation of bugs for each release. Other stats?

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

  • 3.6 release testing is scheduled to start in Sprint 122

  • Environment setup

  • Team responsibilities and owners

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

Link to work in progress page of test plan:

https://openlmis.atlassian.net/wiki/spaces/OP/pages/501580018/Regression+and+Release+Candidate+Test+Plan+work+in+progress

Next steps for 3.6 test plan:

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

@Sam Im (Deactivated) to review reporting link to check if this is the correct one or if it needs to be updated.

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

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

OLMIS5884

https://openlmis.atlassian.net/browse/OLMIS-5884 - Hassan responded and said he would work on ticket and move to QA but it hasn’t been done yet.

https://openlmis.atlassian.net/browse/OLMIS-5888 - Marked as done but not tested. No response from Hassan yet.

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.