Tricks to speed up test management

[#1]

Test management is quite a complex process. Fortunately, there are a few tricks you can apply to make it faster and, as a consequence, easier. Today, we’d like to tell you a bit more about what exactly you can do and how. All these tricks can be applied when using QAlity Plus and we highly encourage you to try it out!

Clone Jira issue (Test Case) to clone it with steps

You might need to create multiple test cases with a very similar test case scenario. For example, imagine you want a distinction between testing environments and you have almost identical test cases – one for Firefox and one for Chrome. You can then clone a particular test case, so you won’t need to rewrite it. When you open a certain issue, there will be three dots in the top right corner. All you need to do is click on them and select Clone. The test case and the steps it contains will then be cloned and saved in the project.

Using keyboard shortcuts 

There are some keyboard shortcuts you can use that will speed up certain activities and help you save a little time. 

• You can use tab to navigate through the test case’s cells and create the next test steps. 
• You can use shift+tab to come back to previous steps.
• Just like in a regular document, you can use keyboard shortcuts to alter your text. Use ctrl+b to bold it, crtl+u to underline, and ctrl+i for the italic. 
• In order to make a clear, visual distinction between different parts, you can leave one step empty. 

Defining and categorizing your QAlity Test issues

• You can add a description of your test in QAlity Test jira issue description.The text will be visible at the top when you move to the test execution, helping you keep track of what’s going on. 
• As these are Jira issues, you can, for example, distinguish test regressions by labeling them as such. So, clicking on this label will result in having a list of all your regression tests and nothing else. Thanks to that, you don’t have to wade through all issues looking for the ones you’re interested in. Moreover, you can add them to a test cycle all at once.  
• You can use custom fields whenever you would like to create a category of information that is unavailable in the default system fields.  For instance, you can choose a text custom field and use it to define your testing area, e.g. feature A and feature B. However, please remember that in order to do that, you need to be logged in as a user with the Jira Administrators' global permission. 

Using JQL filters to see certain issues

You can create a JQL filter with a specific test type so only those will be displayed. For example, you may set a filter to display bugs created during the test case execution.

Head to Filters -> View all filters. In the right corner choose JQL, and type the following command in the search bar:

project= PSP and issuetype = Bug and description ~ "Issue discovered during the" order by created DESC

This will show you all PSP project bugs with “Issue discovered during the" in the description. It will be added automatically, so it’s important to not delete it from the bug description.

Using automation to add extra labels

You can use Jira automation in QAlity Test issues or Bugs created during test execution. For example, you can automatically add a label to the Bugs created with QAlity Plus.

To do that, go to Project settings -> Automation. Once there, click the Create rule button.

To create an automation rule you need to find the right components in the search panel on the right. Build the following scheme:

• When: Issue created
• If: Issue matches JQL

JQL rule you want to use: project= PSP and issuetype = Bug and description ~ "Issue discovered during the" order by created DESC

• Then: Edit issue fields

In our example, we will choose the Edit issue and tick Labels. Then, we will be able to choose a previously created label or create a new one. Let’s create a label called “Discovered_in_QAlity”. On the right, you can type the name and save it.

It will make it easier to organize your bugs. With this kind of label, you will be able to quickly open a link with all these issues, so it will be more convenient to navigate through them.

Bulk update test cases

Whenever you need to change multiple issues, you can save time by changing all of them with one operation. Filter your test cases and choose parameters you’re interested in (e.g. an issue type and a certain date range). Then, click on the three dots at the top right corner and choose bulk change.

You can select all or just the ones you’re interested in. Click Next, and you will be able to:

• Transition multiple issues. Please notice that only one transition bulk operation can be performed at a time and you will need to provide any values required to complete it. For instance, closing multiple issues requires providing a value for the Resolution field (such as Done, Fixed, or Won't Fix).
• Delete multiple issues.
• Move multiple issues. However, they need to be mapped to a project and an issue type. You may also need to map the status, subtasks, and fields of the issues. 
• Watch/stop watching multiple issues.
• Archive multiple issues. It’s worth mentioning that this option allows you to archive a maximum of 1000 issues by default. But, this can be changed by a system admin if necessary. 
• Edit multiple issues; for example, you will be able to bulk-add story points or change the test type. 

After you perform all the changes click Next and then Confirm on the next page. For example, we’ve decided to bulk change assignee for the selected issues:

The result:

Bulk add Test Cases to the Test Cycle

Instead of adding every single test case to the test cycle, you can bulk-add them all at once. In order to do that, open QAlity Plus and go to Filters -> View all filters, and filter the test cases that you want to bulk add to a test cycle.

Next, go to Apps -> QAlity Plus:

Choose the option +Add all QAlity Test issue(s) to Test Cycle. The app will then ask you where and what issues you want to add.

Please notice that bulk change operations can’t be performed by every user. They require the appropriate project-specific permission and the global Bulk Change permission. These can be granted by your project admin.

Summary

This article mentioned a few tricks you can use in your test management in order to gain more time and have a better recognition of what’s going on with your tests. We invite you to try some of these tricks out so there’s some extra convenience added to your test management process. Remember that in case of any questions you can always contact us here. 

If you would like to know more, we recommend reading our other articles here.