You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
To ensure efficient testing, your tests should be organized properly. Today, we would like to present two approaches you could implement with testing software such as QAlity or QAlity Plus. We will also mention the methods you can use that will help you navigate through them, avoid clutter, and not get lost in multiple issue types.
Storing QAlity tests – group QAlity test issues within the project
The first method is to create new QAlity test issues in the project you are currently testing. However, you might end up with a long list of issues, all of them with a “To do” status. To make navigating through them easier, you can use a few tricks such as:
Labelling your QAlity issues will help you find the ones you’re interested in quicker. In order to create labels go to Project settings -> Issue types and choose Labels on the right:
Name the new label, give it a description if you want, and click enter in order to save it.
All labels created like that will later be visible in your QAlity test issue types:
Now all you need to do is click on the label of your choice and your QAlity test issue type will be labeled with it.
You can use checkbox custom fields to mark different types of test cases. In order to create them, go to Project settings -> Issue types -> Task and choose Checkbox from the list on the right.
You can name them, add a description if needed, and click enter.
Same as labels, they will later be visible in your QAlity test Jira issues. Tick the one of your choice and your QAlity test issue type will be categorized with it.
As backlog shows all unresolved Jira issues that are not scheduled for any sprint, all your QAlity test issues will be displayed by default too. However, a project admin can use a JQL filter to determine which issues should and shouldn’t be displayed in the backlog and that includes the QAlity Test issue type. In order to configure it, you need to open the board with the backlog, click on the three-dot menu on the right and select Board settings.
You will see filter settings. Click on Edit Filter Query:
Then, a JQL filter will be displayed and you can choose which Jira issues you want to be displayed. If you don’t select QAlity test issues, they will not be shown when you use this filter.
If you were the one who created the project, all you need to do is click Save and the filter is ready to use. If someone else did it, you will have the option to save the filter under a new name. Click Save as and name the filter. Then, you will be able to find it in the board settings, under “Saved filter”.
Storing QAlity tests – a dedicated project to share test cases
Another way to store your QAlity test issue types is to keep them in a separate project and link to them in particular tasks.
With this approach, you avoid cluttering the backlog. Also, it allows multiple projects to share the same test case base. However, in order for it to work properly, you need to make sure that all the people can access both – those projects as well as the project storing QAlity Tests.
You can organize your tests in Jira by either keeping them in a separate project or creating new QAlity test issues in the project you are currently testing. With the second approach, there are a few ways that will allow smoother navigation through them. These include: adding labels to your QAlity test issues, using custom fields, and linking QAlity test issues to Jira tickets. If you would like to explore more options with QAlity or QAlity plus, we encourage you to see our documentation. Remember that in case of any questions or troubles, you can always contact us or book a demo here.