2017-08-18 QA Meeting notes

Test Cycles and ticket tracking

• How is the progress and tracking going?
  • Sometimes after testing a ticket some acceptance criteria isn't specified enough to validate well, doesn't explain the expected result clear enough
  • First test the ticket and then create the test case (suggestion)
  • Rewrite test cases, read the ticket, may still have to rewrite. This might be a sign that the ticket isn't detailed enough. The most important details could get lost if the ticket is big.
• Sam presented the test cycles to the Product Committee, and they have requested a more detailed discussion to be scheduled.
• Continue adding "Creating test cases" to the acceptance criteria of tickets.
• Make sure all test cases are linked, should have at least one test case per ticket.
• Start the Test Execution when a test case is being completed to continue keeping track.
  
  

 Communication

• Are developers reviewing that test cases have been added before marking a ticket as done?
• We will need a video showcase for the regression testing in Sprint 33