/
2018-11-05 QA Weekly Meeting notes

2018-11-05 QA Weekly Meeting notes

Nov 15, 2018

Date

Nov 5, 2018

Attendees

  • @Sam Im (Deactivated)

  • @Joanna Bebak (Deactivated)

  • @Joanna Szymańska (Deactivated)

Goals

  • Bug triage

  • Release Planning & Assignments

  • Reporting test plan

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes



Bug Triage: review the following bugs and prioritize 

https://openlmis.atlassian.net/browse/OLMIS-5637 : @Joanna Bebak (Deactivated) to create a new test case for editing requisition template and validating the UI & print match

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

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









3.5 Release Candidate test plan

  • Risk 1: When to schedule (Starts in Sprint 113)

    • Still in discussion on when to start Release Candidate testing due to Zambia trip (Nov 26-30)

    • Can we start regression testing and Malawi UAT with a smaller subset of team members during that week of Nov 26th?

    • Plan release candidate testing for a longer period of time?

    • Do we need to start testing on Nov 22nd? Can we start on Monday 19th instead?



  • Status of test plan creation

    • Reorganizing testing to focus on new features first, then regression testing

      • Should we label test cases for 3.5 with the 3.5 version to test first? Will that overlap with regression test cases? @Joanna Bebak (Deactivated) 

        • @Joanna Szymańska (Deactivated) What about test cases for mCSD?

      • One bug triage after all the new feature testing is done?

    • Reviewing test cases created by other teams and adding them to the CoreRegression label OR has this been discussed in Tech Committee?

  • Where do we expect to be with functional testing by the time we start release testing?



Tasks before Release Candidate testing starts:

Environments need to be created https://openlmis.atlassian.net/browse/OLMIS-5603
Need to let Josh know in advance how many environments we want to set up 
Who will own each environment? Teams have designated a lead during testing
Resources: Do we have additional resources for testing? Team Ona has added a QA resource
Communication (before we start and during @Joanna Bebak (Deactivated) & @Joanna Szymańska (Deactivated) will be responsible)
All slack channels (QA, General, Malawi) need to be notified that testing is starting two days before
Everyone needs to be notified when testing has started
Everyone is notified of testing status daily
@Joanna Bebak (Deactivated) to link from Test strategy: Exploratory testing & Batch Approval testing - this needs to be explained for testers, or someone will need to own this to make sure it happens 
Reviewing test cases from JSI before adding them to release candidate testing (has been done by @Joanna Szymańska (Deactivated))
Reporting test plan: We need to work with Craig and Clay to understand what is needed to test reporting, who will test, and add details to test plan (@Joanna Bebak (Deactivated) and @Joanna Szymańska (Deactivated) to attend meeting)

Bugs that must be fixed before release candidate

Blocker and critical bugs
Malawi bugs?

Setting up and managing bug triage

Should we have a daily bug triage? Or should it be every couple of days?
Core and Malawi should be included
Monitoring Malawi UAT



@Sam Im (Deactivated)

Create different test cycles for each team that contain multiple components in each test cycle.

Reorganize test cases by new features first?







Reviewing test cases when they are new: Test cases that haven't been reviewed should be in a QA status. QA person will review test case and decide if the test is a CoreRegression testing. 

Every 2-3 sprints, review test cases that were tested or impacted by the most recent changes. Check test cases to ensure they are still valid and steps are correct.



Action items

OpenLMIS: the global initiative for powerful LMIS software