In JIRA, you are creating new test runs in a project. These test runs are organized under projects they are created within.
This is the version the test run belongs to. You can create different Versions for a project. These versions appear in the Fix Version field on the Create Issue screen. You can add one or more versions that relate to the test run. Clicking on the version of a test runs displays all the test runs that belong to that particular version. It makes bulk changes easier like a big number of test runs can be made a part of another Fix Version to being over the entire regression suite from one Fix Version to another. If no version is assigned to a test run, then it appears under “Unscheduled”.
Labels are created by users to tag the test runs with. Users do not need to have Administrator privileges to create new Labels or re-use the existing ones. If the test run has not been assigned a Label, then it appears under “No Label”.
If the Administrator has created different Components in JIRA, then you can relate test runs to these Components. The Component field populates that many options to select. You can select multiple components for a test run. “Component” also plays a role in organizing the test runs. If the test run has not been assigned a component, then it appears under “No Component”. Clicking on the component of a test runs displays all the test runs that belong to that particular component.
In JIRA test runs, same as other issues, can be organized by their Sprint they are covered within. Test Runs that are covered under the sprint that is currently active, are displayed under Active Sprint. Test Runs that are covered under the sprint that is already completed and not active, are displayed under Completed Sprint.
Open a test run and click its –
- Active Sprint to view the sprint on the scrum board
- Completed Sprint to view the Sprint Report for the sprint