How to manage testing progression during a sprint

When a sprint has started the test case creation and execution must be managed daily to ensure complete test case coverage. This page explains where to go, what to do, and what needs to be tracked. Each section should be reviewed daily.

Step-by-step guide

View Test Cycle for the sprint

  1. Go to JIRA, then click on Tests, Plan Test Cycle. Select Versions 3.2.1 (or whichever release version for this sprint).
  2. All the test cycles for the sprint will display. There should be at least one for the sprint called "Test Cycle for Sprint XX", there may also be a regression test cycle, and there is the generic Ad hoc test cycle that the system has created.
  3. Test cases MUST be linked to the Test Cycle so that the execution and metrics are tracked. 
  4. If a test case has been created but not assigned to a test cycle, then you can add them here. Select the test cycle you want to add a test to, then click on the gear button on the right and click "Add Test". Select the tests that need to be added.


View Test Case creation during the sprint

  1. Go to #QA Slack channel every day. If there are any test cases that need to be created for the sprint, the tester will post in the slack channel as they are creating them.
  2. To check for yourself: Go to JIRA, click on Active Sprints, this should display all the JIRA tickets assigned to the current sprint.
  3. Go through each JIRA ticket and check to see if a Test Case is linked. If a test case is not linked, then these are the test cases that will need to be created or linked (if a test case already exists for this but hasn't been linked to the JIRA ticket). Post questions in the #QA Slack Channel as the JIRA tickets move to QA. If the tickets are moved to QA but no test case has been created or linked, then they should be mentioned in the slack channel for the tester (Joanna or a developer) to create or link.
  4. Or create the test case if needed.


View Test Case Execution 

  1. Go to this link to view the progress of test case execution: OpenLMIS Test Metrics Dashboard
  2. For each JIRA ticket, there should be a corresponding Test Case; unless the JIRA ticket is a task or a documentation ticket. (Example: 10 JIRA tickets = 10 Zephyr test cases on this dashboard.)
  3. As JIRA tickets are moved to QA or Done, the execution status for the linked Zephyr test cases should change from Unexecuted, to WIP, then to Pass or Fail. Test Execution doesn't typically happen until a couple of days into the sprint because the developers are working on the ticket. By Day 3 of the sprint, test cases should start changing statuses. 
    1. If the status hasn't changed for any ticket by Day 3 of the sprint, then you should check the team's end of day status in the #general Slack channel. They may be blocked on development, or not far enough in development to pass on to QA. If by Day 5 there has still been no progress, then notify Brandon to follow up on ticket status.