2017-10-02 Meeting notes

5 min

Happy October! Let's check in

@Sam Im (Deactivated)

• Is the occurrence for this meeting enough? Mondays still ok?

• How should I get more feedback on agenda items for each week so everyone has input?

 25 min

Retrospective ideas and action items 

@Sam Im (Deactivated)

@Joanna Bebak (Deactivated)

• "Not sure how to write testing stuff in tickets" — Team ILL retrospective idea

  • Testing with AC doesn't always get edge cases or design decisions that are made in development

    The person assigned to the ticket should be responsible for updating the AC based on changes in the comments.

    Exploratory testing is testing not related or tied to any ticket within the current sprint. The focus is on the UI for this type of testing. Joanna has currently found a few bugs and logged them for Sprint 36.

    The testing is done manually through the UI, vs using the API — that needs to be captured

• Need more detail than just "Create test case and link to ticket"

• "automated tests are not visible/documented in a way implementers and stakeholders can read them" — Team ILL retrospective idea

• Need to start working on contract testing tickets

  • OLMIS-2926 is ticket in current sprint to change contract tests to use demo data. This should be finished before we start adding contract test tickets to the next sprint.

• Browserstack!

• Determine details of showcase and regression

  • We should determine a rule of who shows which part of the regression during the showcase. Best idea for Joanna to show what she's done, and Sam to show her testing. 

  • When regression test cycle is ready, we don't have clear assignments in the beginning. Division of work is needed at the beginning.

30 min

Regression testing

@Sam Im (Deactivated)

• What are we regression testing in Sprint 36?

  • Regression testing should support the release. There are also lots of bugs this sprint to test.

  • Requisition testing from end to end. Delete and Reject requisitions. 

  • @Sam Im (Deactivated) will create the test cycle and add the test cases. 

  • @Joanna Bebak (Deactivated) will assign the test cases for the test cycle.

• Should we still create a ticket for regression testing?

  • @Joanna Bebak (Deactivated) will create ticket for regression testing in Sprint 36

• How can we better plan regression testing before the sprint starts?

  • Plan for the regression testing cycle on the 2nd QA meeting, before the beginning of the next sprint. 10/9 (may be 10/10 instead) meeting we focus on testing for next sprint. (Look at the grooming page during the call.)

  • Before Sprint Planning we should know what the regression testing will be for the next sprint.