Log Issues

Log Issues while Recording

You can log issues to the scenario while recording the test session. The issues get logged into the Issue module of QMetry. If external trackers are linked with QMetry, the issue gets logged into that external tracker.

Note: The logging issue operation will pause your session for a while. If you wish to resume the session, then close the issue logging screen after logging the issue.

 

  1. Click on the Bug icon

     

  2. The screenshot of the current page opens in a separate tab.

  3. The page also has options like any other image editor.

Annotating Screenshot: You can annotate the screenshot you captured using the features available on the editor. It allows to describe any bug or issue more precisely, which ultimately makes it more comprehensive.

 

Logging an Issue in QMetry

Users can now log the issue with the QMetry field values like the following. If the https://qmetrysupport.atlassian.net/wiki/spaces/QTMS810/pages/3044925085 feature is enabled, then the fields on the Issue create screen appear in accordance with the layout defined for the Add page of the Issue module.

  • Project: Select the project for which the issue is to be logged.

  • Summary: Enter the Summary that represents a brief about the issue.

  • Priority: Select the priority of the issue from the drop-down list.

  • Labels: Select the Labels applicable to the issue. You can select multiple options for the field.

  • Issue Type: Select the issue type from Bug, Enhancement, New Feature.

  • Owner: Select the assignee who will work on the issue from the drop-down list.

  • Description: Describe the issue in detail in this text area.

Logging an Issue in Jira

If Jira is configured with the project in QMetry, then you can log the issue directly in Jira.

  • Project: This is QMetry project with which Jira is integrated. This project is selected by default here.

  • Instance: Select the Jira instance to which you want to log the issue.

  • External Project: The External Project field values populate according to the instance selection. Select the Jira Project you want to log the issue to.

  • Issue Type: The issue type is displayed as per the issue type configuration with QMetry Issue module while Jira integration.

Other fields will appear in accordance with project selection.

Logging an Issue in Rally

If Rally is configured with the project in QMetry, then you can log the issue directly in Rally.

  • Project: This is QMetry project with which Rally is integrated. This project is selected by default here.

  • Instance: Select the Rally instance to which you want to log the issue.

  • External Project: The External Project field values populate according to the instance selection. Workspace relevant to the projects are displayed in parenthesis. Select the Rally Project you want to log issue to.

  • Issue Type: The issue type is displayed as per the issue type configuration with QMetry Issue module while Rally integration.

Fill all the required details on the form and then click on the Log Issue button.

 

 

 

Clicking on the External Key opens the issue detail page in Rally.

If you click the Entity Key of the Exploratory session, it opens the QMetry Issue module. In QMetry the issue is created in the Issues module. The screenshot is added as an attachment to the issue in the Issue module.

Clicking on External Key opens the issue detail page in Rally.

 

Logging an Issue in Azure DevOps

If Azure DevOps is configured with the project in QMetry, then you can log issue directly in Azure DevOps.

  • Project: This is QMetry project. QMetry project with which Azure DevOps is integrated is selected by default here.

  • Instance: Select the Azure DevOps instance to which you want to log the issue.

  • External Project: The External Project field values populate according to the instance selection. Select the Azure DevOps Project you want to log issue to.

  • Issue Type: The issue type is displayed as per the issue type configuration with QMetry Issue module while Azure DevOps integration.

Fill all the required details on the form and then click on the Log Issue button. The screenshot is added as an attachment to the issue in the Issue module.

 

 

The defect count is displayed for the recorded session on the Exploratory Testing screen.

Click on the Defect count to navigate to the Defects tab of the session.

 

The Defects tab displays details of the logged defect.

Clicking on the External Key opens the issue detail page in Azure DevOps.

 

If you click the Entity Key of the Exploratory session, it opens the QMetry Issue module, where the issues is displayed with External Key clicking on which opens the issue detail page in Azure DevOps.

View Logged Issues

Issue Logged in QMetry

In QMetry, go to Automation > Exploratory Testing.

You can see the count of issues logged for the tests/sessions.

On clicking on the issue count in the grid opens the issue screenshot attached in support of the issue.

You can view the details related to the issue.
Clicking on the Entity Key, it opens the issue detail page in the Issue Module.

Issue Logged in Jira

When you click External Key for the Exploratory session, it opens issue detail page in the external tracker.

In QMetry, you can view the available External issues when you go to log issues from the Execution Screen.

Go to the Execution Screen. Click the Bug icon. It opens the Issues screen.

The issues logged from QMetry Exploratory extension can be seen in the Available Issues tab on the Issues screen.

Log Issues without Sessions

You may come across certain issues that you can not associate with a session instantly. QMetry Exploratory Testing allows you to log issues even without recording a session.

Issues, logged without session, are added to the Issue module in QMetry Test Management.

Steps

Open the QMetry Exploratory Testing add-on.

Click on the Log Issue button at top right corner of the QMetry Exploratory Testing extension main screen.

It captures the screenshot of the website screen currently open.

Enter issue details same as you do when logging an issue during recording the session.

The issue is added to QMetry Issue module in the corresponding project.