Adding/Linking Issues to Test Case and Test Step

Introduction

Users can log bugs at test case as well as test step level. Users can add issues and attachments to test steps. It allows users to log bugs and attach test run logs at step level. The attachments are also displayed on the Test Executions tab of the test case.

On the Test Run screen, click on the Bug icon for the test case you want to log issues for. The Bug icon turns red once you add a bug.





It opens issues screen.

Issues Screen

The Issues screen has these tabs on it: Available Issues, Linked Issues, Link New Issues, and Link External Issue.



A. Jira Instance and Jira Project: You can link issues from multiple instances and across projects. The Project drop-down displays configured projects on which you have access over.

B. Available Issues: The tab shows issues added under the project and are available to link with the test case.

  • Issues from External Tracker: If you have configured external tracker with QMetry project and issues are logged in the tracker, then those issues are displayed with External Key.

C. Linked Issues: The tab shows issues already linked with the test case.

D. Link New Issues: The tab opens Create Issue screen. Add new issues and link them directly with the test case. The linked issue is displayed under the Linked Issues tab. The test case steps are added as Description.

E. Click on the Link icon to link individual issue to the test case.

To link multiple issues in one go, select the issues and click either on the Link button or the Link & Close button.





Issue IDs of the issues associated with the test case appear on the Linked Issues tab. Clicking on Issue ID link opens the Issue details page in QMetry.

Issues already linked to the test case are displayed on the grid with the details of Summary, Ext ID, Platform, and Linked Date. The details help users understand for which platform a particular defect was logged.

Link New Issues

  1. On the Test Run Screen, click the Bug icon for test case to which the issue is being added.

  2. Open the Link New Issue tab to add issues and link it to the test case.

  3. When a new issue is logged ((in QMetry as well as in Jira) ) from the execution screen, the Issue Summary field will be auto-filled with Test Case ID and Test Case Summary for easy reference to the relevant test case the bug is logged for.

  4. The Description field populates with Test Case Summary and Test Step details.

  5. Follow the same process of adding an issue from the Issue module. Enter the issue details and click Create.

  6. Once you add an issue, it is automatically linked to the test case and it is displayed on the Linked Issues tab.

Linking Existing Issues

  1. On the Test Run Screen, click on the Bug icon.

  2. The Issues screen opens.

  3. Open the Available Issues tab. It shows issues available to link with the test case. Issues added in QMetry as well as in External Tracker are displayed on the screen. Issues added in External Tracker can be identified by its External Key.

  4. Select issues on the screen and click on the Link button.

Log Jira Issues from QMetry

If Jira is configured with QMetry project, then the Issue module in QMetry will not be available. Defects in Jira can be logged from Execution Screen of QMetry.

Logging an issue for the First Time

You will be asked for Jira authentication through pop-up.

Note: Enter Jira Username and Password (if Server Jira) or API Token (if Cloud Jira) to authenticate and modify the Jira entity based on provided user credentials.

  • Username: Enter Username.

  • Password/API Token: Enter Password.

To Edit/Revoke Authentication

If your Jira credentials are changed, then follow https://qmetrysupport.atlassian.net/wiki/spaces/QTMS862/pages/1522046380/Projects+using+Jira+integration+for+Issue+%28Bug%29+Tracking to read about Revoke Authentication to modify the credentials in QMetry.

On the Test Run Screen, click the Bug icon for test case/step to which the issue is being added.

1. Open the Create Issue tab to add issues and link it to the test case.

2. Jira Instance and Jira Project: It shows the Jira instance and Jira project that has been configured with your current QMetry project. Select the Jira instance and project to which the issue is to be added.

3. The Description field: Issues raised to Jira from Test Execution Screen of QMetry fields includes field values from QMetry.

The following fields will be auto populated from QMetry test case to Jira issue Description field:

  • Test Case Summary

  • Test Case Description

  • Comment

  • Step details:

    • Step Description

    • Step Input Data

    • Step Expected Outcome

    • Step Actual Outcome

    • Execution Status

    • Comment

Issue name will be appended with QMetry Test Case ID.

You have to fill other details of issue like Label, Priority, Type along with Reporter and Assigned To fields.

Making Reporter field mandatory while creating issue: Refer to Making Reporter field mandatory for more details.



4. Follow the same process of adding an issue from the Issue module. Enter the issue details and click on the Create and Link button.

The issues is generated with Jira ID. 

Once you add an issue, it is automatically linked to the test case and it is displayed on the Linked Issues tab.

It also displays the Linkage Level i.e. Test Case or Test Step to which the issue has been logged.



The Available Issues tab displays issues that can be linked to the test case.

External Issues are identified with their External Key. 

To link a single issue, just click on the individual link icon.

To link multiple issues at a time, select issues and then click on the Link Selected Issues at the bottom.

Unlinking Issues

You can remove the issue linkage. To unlink a linked issue, open the Linked Issues tab.

In case of individual issue, click the Unlink icon for that issue.

To unlink multiple issues at a time, select issues and then click on the Unlink button.

Issues Linked to Test Step

Issues linked at Test Steps will be displayed at Test Case on the execution screen.

Users can view step level bugs at test case level because they want to see the all associated bugs at Test Case level.

Bugs are linked to a particular version of test case and test steps under that test case. For example, on the Execution screen, a bug is logged with TC1 Version 1. Now the test case details are updated and the test case is saved with Version 2. When the test case version is synced on the Execution screen, the bug will only be displayed with the earlier version.

On Execution Screen, hovering over the Bug icon displays two distinct count - issues linked to test case and issues linked to test steps.

 

  • On test case list view, the Linked Issues Count column displays count of issues linked at test steps level as well as test case level.

  • On test case detail page, the Issues tab displays Linkage Level of issue along with Test Case Version.

  • On Issue detail screen, the Execution Runs tab the grid displays Linkage Level of issue along with Test Case Version.