How to report and link bugs to test executions with QAlity Plus

[#1]

Keeping track of bugs reported during test executions is an important part of assuring the quality of the product. It can help us make sure that the bugs are appropriately taken care of. Additionally, we can use this information for further analysis, such as which parts of the system are causing the most problems. Testers can also use this knowledge for any subsequent tests. First - to not duplicate already existing bugs, second to understand which problems tend to come back (regressions).

This guide explains how you can easily report and link bugs during test executions using QAlity Plus - Test Management for Jira - a tool that boosts the efficiency of testers and gives the whole team visibility into the testing status.

1. Enter the test execution

You can execute a test in QAlity Plus either directly via a test case, or via a testing cycle.

To execute a test from the test case view, enter the test case menu, and select Execute

To execute a test via a testing cycle, go to the test cycle, select the test cases tab, and then click Open execution next to the test that you want to execute.

2. Click on the + icon in the bugs column

Once you spot a bug during the test execution, you can create a bug directly from your current test execution. To do so click on the + icon that is located on the Bugs column and then click on +Create New. You will be shown a standard Jira issue creation dialog.

Once you are done filling in the details for your bug, create the issue, and it will be automatically linked to your test execution step!

If you know that a bug you encountered already exists in the team's backlog, you can choose to search and link the bug, instead of creating a new one. This helps avoid having multiple Jira issues to tackle the same problem and keeps your backlog clean. To search for a bug to link, simply start typing the issue key or issue summary into the Search bugs… input. 

3. Easily access status of reported bugs

Once your bugs are linked to test execution steps, you can easily track their status. While you browse the test execution, click the link in the Bugs column and you will be shown all of the bugs reported in this step including their status.

In addition to this, you also have an insight into all bugs that have ever been reported as a part of this test execution. Scroll down to the Past Executions section to view the list of all reported bugs.

That wasn’t difficult, was it? QAlity Plus - Test Management for Jira is available on the Atlassian Marketplace for Jira Cloud and Jira Data Center.

[Ivana Sizer]

Hi, 

I need to run the Tracebility reort  and see the bugs and their severity columns and I am not able to see it there, what am I missing? We are using QAlity, not QAlity Plus. Do I need to upgrade it to QAlity Plus in order to be able to link the bugs??

How to report and link bugs to test executions with QAlity Plus

Many thanks.

Ivana

[Sebastian Brudziński]

Hello @Ivana Sizer 

you are correct, both the traceability report and linking bugs to test execution steps are only available in QAlity Plus.

Bets regards,
Sebastian

[Ivana Sizer]

Thank you so much Sebastian.

Ivana

[Ivana Sizer]

Hi Sebastian, 

another quick question:  How do you gather bus requirements with Jira board when having only Qality plus, which is great, but I am missing capturing the requirements as a part of full-cycle test management for managing the test cases and requirements as well as Jira issues. At the moment, I am missing creation of the test folders covering various epics, like for example the Tricentis Test Management tool brings.

How can I create that sort of test design, with viewing the test folders, I used to have that xray plugin as well in other job. 

[Neha Nimgire]

Hi Sebastian, 

I want to know if it is possible to assign a execution user to multiple test cases in the test cycle. This page https://soldevelo.atlassian.net/wiki/spaces/QS/pages/3484221592/Assigning+users+to+test+case+execution+PLUS only mentions how you can assign user to each test case one by one. Is there a way to do this in bulk ?

Thanks,

Neha

[Michał Kowalewski_SolDevelo]

Hi @Neha Nimgire and welcome to the community!

I'm happy to inform you that today we implemented a possibility to change the assignee in bulk in the test cycle. Please take a look:

We hope you'll like this new feature! Feel free to let me know if you have more questions regarding our products.

Kind regards,
Michał
SolDevelo Team

[Johanna Gutierrez]

Hi @Michał Kowalewski_SolDevelo 

I have the doubt of how to make the number of executions increase, what does it depend on for the number of executions to increase ?

Best regards,

Johanna Gutierrez

[Michał Kowalewski_SolDevelo]

Hi @Johanna Gutierrez 

You can execute a particular test case as many times you want.

The execution can be performed in two ways:

• Ad Hoc → meaning the test case is executed without any test cycle. Such an execution can be started directly from the test case, for example, from your Jira board.
  
  
• Test Cycle → you can add your test cases to the cycle. Once the test case is added to the cycle, then a new execution is created.

These both ways allow you to increase your executions. Please let me know if it answers your questions.

Kind regards,
Michał
SolDevelo Team 

[Johanna Gutierrez]

Hello @Michał Kowalewski ,

Certainly, I've performed executions from both locations you mentioned. However, if I execute using the "Execute" button, my previously created "test cycle" doesn't appear. When I execute from the test cycle folder, the execution count doesn't increase.

Thank you very much for your assistance!

[Michał Kowalewski_SolDevelo]

Hi @Johanna Gutierrez 

When executing, for example, directly from your Jira issue, please make sure that the test case you'd like to execute is already added to the test cycle. Then, the cycle should appear on the list.

When it comes to the execution increase, where exactly do you check if this number has increased?

Please feel free to contact us here through our customer portal. We will be able to clarify your request faster.

Kind regards,
Michał
SolDevelo Team 

[Alla Ovcharenko]

Is it possible to create a bug from the test case with no steps? 

[Michał Kowalewski_SolDevelo]

Hi @Alla Ovcharenko and welcome to the community!

The test steps are required to be able to create a bug while executing the test case. Would you be so kind and provide me with more context why you'd like to have such an option? What's your use case? We're happy to gather feedback and suggestions.

If you prefer, you can contact us here to describe your request.

Kind regards,
Michał
SolDevelo Team