...
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.
Creating a Test Cycle
Test Cycles are used to manage and monitor the execution of test cases within a sprint, or within a special cycle such as a regression test cycle before a release. A Test Cycle must be created for each occurrence of testing within the sprint. Zephyr restricts running test cases within a scheduled test cycle, so if a test case must be rerun then a new Test Cycle must be created and the QA lead will assign the appropriate test cases to the new Test Cycle.
Creating a regular sprint test cycle:
1) In Jira go to Tests, then select Plan a Test Cycle.
The regular sprint Test Cycle will look like this, enter the Version expected to support this testing, the Test Cycle Name, and the environment where the testing will be done. f the version is unknown, you can select "Unscheduled".
Add Test Cases to the Test Cycle:
Go to the Test Cycle you created and click the gear icon to the right and click "Add Tests".
Test cases can be added individually, by a search filter or by another cycle. If you are copying all the test cases from a previous cycle, for example a regression test cycle, then you should choose "From Another Cycle" option.
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 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.
...
Select the Component or Label and enter in the component name or label name and search.
Click Save As to save the search filter so that it can be used to pull in all associated test cases when creating a test cycle.