Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

(warning) Be aware that the screenshots may not match Jira or Zephyr UI exactly due to each system's version updates. 

Viewing JIRA tickets

Each development issue within a sprint is tracked by a JIRA ticket. The JIRA tickets contain the acceptance criteria for development, and can also be used to create the expected results for test cases. JIRA tickets are linked to test cases to ensure traceability to requirements. This is an example of a JIRA ticket and its acceptance criteria.


To create a test cycle using a search filter, you must first create the search filter. For regression test cases we have filters based on a label (Regressions, CCE, StockManagement, and Administration).

Creating a Test Case

Test Cases

Test Cases should be created for each JIRA ticket that is assigned to a sprint and related to a release. Its advised to create test cases before a sprint begins, but this can also be done once a sprint has started. Test cases are not required for tasks or documentation tickets. 

Please refer to this live document to follow detailed guidance on test case creation: Regression Testing guide and improvements

See below for a general guidance on test case creation:

Creating a test case:

1) In JIRA, click on Create. Select the Project, in this case the project is OpenLMIS General. Then select the Issue Type as Test. The Summary, Components, and Description can be copied from the ticket to keep consistency, or help in rewriting the test case in the next steps. Click Create and a JIRA notification will pop up with the Test Case number.


5) Once the issue has been resolved by the developer, they the developer must reassign the Jira ticket to the QA person, notify them either via Slack channel or directly, and then the QA person must execute the test case again. It is the team's responsibility, as well as the developer's responsibility, to ensure any tickets in the QA column are being moved and progressed during a sprint.

During regression testing, if a test step fails and there is a different result, or an error appears that is not expected, then a defect must be entered. The steps to create a defect are detailed below.


When detailing the steps to reproduce the bug, it is also helpful that you walk through these steps and attempt to reproduce the bug yourself.  Please add notes in the description when this has been successfully reproduced by you.

The Environment should be either or , and you should provide as much detail about the environment that would help a developer when reproducing the bug, such as in which browser you tested (Chrome or Firefox).