qTest Manager Integration with JIRA

How to set up a qTest JIRA integration.

Learn how to easily set up a real-time integration with qTest JIRA with the most powerful agile test case management platform for software testing.

In this video we will help you to integrate with JIRA at both the requirements and defects level.  

Install Marketplace Add-on

On the Atlassian marketplace, make sure you install the qTest for JIRA Test Management add-on to either your JIRA Cloud or Server instance.   This adds enhanced issue and project level reporting with qTest Manager integration.  

Setup JIRA Connection

Once installed, navigate to the qTest Integration settings located in the top navigation bar.  Then select JIRA in the left navigation panel.

If you are integrating with JIRA Server, please take note that you will need to white list inbound and outbound requests from certain qTest Cloud IP addresses to have a successful integration.

For more information, please see the JIRA integration walk through guide for connecting with JIRA server on support.qasymphony.com

Give you connection and name, along with the correct URL for your JIRA instance.  Then, using JIRA admin credentials, enter the username and password

Be sure to test the connection first, then click the save and configure button.

During this part of the integration, you have the option to integrate with JIRA issue as defects and requirements.  

Establish Bug Issue and Defect Integration

Here I’m adding to Bug Issues types that I want to report as defects into JIRA when I run a Test Execution.

Optionally turn on the requirement integration and then chose which JIRA issue types you want to show test coverage against.  These could be user stories or custom issue types.

Once your project has been refreshed, select the wrench in the actions area to configure how you want your JIRA issues organized in qTest Manager to establish test coverage

Establish Issue and Requirements Coverage

JIRA issues types can be pulled into qTest Manager from an entire JIRA project, or if using a favorite filter, can be narrowed to only pull in the issues your team care about.

qTest Manager will automatically organize your issues based off JIRA property values, such as Sprint and Status while also displaying the properties fields your team needs to see.

Save the configuration, and click the retrieve data button to establish a real-time integration.  If a new JIRA issue is added after the retrieval, don’t worry; we will send any newly added JIRA issues and changes to JIRA property fields in real-time back to qTest Manager.

Click on a JIRA issue to see the most up to date property values, from here, you can link test cases from our test design repository or create a test case directly on the JIRA issue.

After tests are added, you can quickly access JIRA through the issue link in the properties area.  On the JIRA issue, qTest Manager will now displays the case values (such as version, and Approval)  and the latest execution run, along with actionable links to get back into qTest Manager.  

Here I’m clicking a test link to be brought to our test design module to make any edits to my template.

Select Test Execution to start running tests and report Defects into JIRA.

Test JIRA Issues

When setting up your runs, qTest Manager allows you to pull in associated test cases with their JIRA requirements, this allows rapid execution setup for JIRA test coverage.

Select the test you want to run, then click the run button to execute.  As I walk through the Test Steps, I can mark execution status and then click the bug Icon to either link to or create a new JIRA issue.

Here I’m selecting multiple configurations to execute so I can generate variable run coverage for my JIRA issue.

After saving, select the Test Runs you wish to execute and then click the run button.

Within the Test Pad, users can easily mark step status.  In this example, I want to create a new JIRA issue against a failed step.  Click the bug ID and include all steps to reproduce.  

With our real time integration, qTest Manager will open a native JIRA submission form and also auto populate test steps into the description field so development can easily trace steps to the failure.  

Once submitted, qTest Manager will push automatically close the window and provide defect links at the Test Run and Test step.

In qTest Manager, testers can see defect summary view with associated test runs, and leverage JIRA links easily hop back into their JIRA projects.

In JIRA, your development team can see the Test Run execution that reported the defect and view any associated requirement issues,

Back on our initial JIRA user story, we can now see the latest execution status and which test runs still need to be ran for test coverage.
This helps teams understand when issue can be moved to a done status based of the executed and unexecuted tests runs.

Explore More

Get Started with QASymphony