Menu

Submit Defects in Test Execution for Manager 9.0 and Previously Released Versions

Overview

You can log a defect if a test run fails or requires additional development effort. There are various ways you can submit a defect from the Test Execution area:

  • You can use the Quick Run or TestPad window to submit a defect DURING test execution. For more details on Quick Run and the TestPad, read Executing Test RunsDetails are below.
  • Use the Test Log in Execution History to submit a defect AFTER executing a test run. See details below.

This article explains how to submit defects to qTest Manager as well as JIRA. Read the Submitting Defects sections within each Integration Guide if you use another tool to track your defects.

Submit Defect During Test Execution

You can submit Defects from an individual Test Step Log or from an entire Test Log in the TestPad. Alternatively, you can submit Defects from a Test Log in the Quick Run window. Either way, when you click on the Bug icon, the New Defect Submission Form pops up so that you can input the relevant Defect information to create a new defect. Click Save or Save & Close.

TestPad

Quick Run

Submit Defect After Test Execution in Test Log

If you forgot to submit the defect during test execution, you can submit a defect or link to an existing defect from the appropriate Test Run's Test Log.

You can also use this feature when reporting failed results from Jenkins/Bamboo or through qTest's Automation Scheduling capabilities.

  1. Navigate to the appropriate Test Run and select the Execution History tab.
  2. Find the Test Log line item for which you want to submit a defect.
  3. Select the Bug icon:
    • from the Test Log line item to submit/link defects for an entire Test Log
    • in the Test Log Details to submit/link Defects to individual Test Steps of an executed Test Log
  4. The Submit/Link Defects widget opens.
  5. Select New to submit a defect linked to the Test Log. The New Defect window opens. Enter the required information.
  6. If you want to link the Test Log/Test Step to an existing defect:
    • enter the Defect ID (if known) and select Link
    • or select Search to search for defects using keywords.
  7. Once you enter the defect, you can close the widget.
    Note: To remove a linked Defect out of the Test Log select the Delete icon.

Autopopulating Defect Data 

By default, your Defect's Description field will only auto-fill with the Test Steps Description when you submit a Defect linked to an individual Test Step.  

To configure more fields with auto-fill behavior, you can set this up in Field Settings under the defect artifact.  If using JIRA, this can be set up in the project's Integration Settings area.

Using qTest Manager Defects

Submit a New Defect in Manager 

  1. Select the Defect (bug) icon for the Test Step that failed.
  2. The Submit/Link Defects widget opens.
  3. Select the Include all test step details checkbox on the widget.  
    • We recommend selecting this checkbox so that when a developer reviews this defect, they will understand the steps to reproduce it.
  4. Select the New button.  The New Defect window displays.  
  5. In the Summary field, enter the name of the defect.  
  6. Complete the additional fields.
    Note: The fields on the page are created in Field Settings and determined by the user.  If you select the ‘Include all test step details’ checkbox, all of the steps leading up to where the test failed will copy from the test run to the Description area of the New Defect page.  If you wish, you can take a screenshot of the error and upload it to the Attachment section of the Test Step or the Test Run.             
  7. Click the Save & Close button to save the defect and close the screen.  The Test Pad or Quick Run window will reload.
  8. To verify the defect has been created, move the cursor to the Test Step that failed and select the Defect (bug) icon. The ID for the defect, summary of the defect, and defect status (‘New’) will display.
  9. In the 'Mark test run’s Status as' field on the TestPad, select the down arrow to open the drop-down and select 'Failed.
  10. Save.                                             

Link to an Existing Defect in Manager

  1. Select the Bug icon for the Test Step that failed.
  2. The Submit/Link Defects widget opens.
  3. Enter the existing Defect ID in the Enter Defect ID field.
    link_existing_defect.png
  4. Select Link to link the defect to the existing defect.  
  5. At the top of the TestPad, select the status of the test run.
  6. Save and then close the Test Pad.
    Note: To view the defect that was linked to the test run, select Reload to refresh the page and then navigate to the Test Run that was just executed. Select the bug icon in the Execution History area of the Test Run page.  Then, click the link for the Defect ID to display the defect.

Review Defects in Manager

In qTest Test Execution, you can find defect information in many areas:

Test Run page:

  • To view defects in a particular Test Log, select the defect icon from the Execution History grid.
  • For an aggregate list, select the Defects tab for a roll-up of all defects related to any of the test logs of the Test Run. The Defects tab can be customized so you can display additional Defect fields as columns. 

Test Suite, Cycle, and Release pages:

  • To view defects for a single Test Run, select the Defect icon from the Test Run grid.
  • For an aggregate list, select the Defect Summary tab for a roll-up of all defects related to associated Test Runs. This Defect Summary tab can be customized so that you can display additional Defect fields as columns. 

For advanced reporting, use qTest Insights to gain more defect visibility.  

Using JIRA Defect Integration

Before you submit a defect from qTest Manager to JIRA, make sure you have correctly set up your integration and installed the browser plugin from the resource center.

The browser plugin allows for a native submission experience to JIRA so you are not required to constantly map system fields. This plugin requires no settings and works immediately upon installation.  

Browser_exention.gif

Submit a New Defect into Jira

  1. Select the Defect (bug) icon for the step that failed. 
  2. The Submit/Link Defects widget opens.
  3. Select the New button.
    submit_defect_widget_new_button.png
  4. The Select a Defect Type widget is displayed.
    select_a_defect_type_widget.png
  5. Leave the Defect Project field blank.
    H
    INT: Recall during setup that on the JIRA Integration Configuration page, you selected a JIRA project and JIRA issue type.  When you want to create a defect, the system asks you what JIRA project and Issue type you want to select.  
  6. In the Defect Type field drop-down list, select the JIRA project and JIRA issue type that represents the defect (e.g., bug, task, etc.) to create in JIRA. 
  7. Select OK.
    Note: If the browser plugin is not correctly installed, or you decide to not install it due to your company’s security policies, the Defect Submission window in qTest Manager is displayed.
  8. Fill in all necessary details with regard to how your team enters a JIRA ticket for a bug. The steps that reproduce the test, up to where the test failed are auto-populated in the Description field.  Complete the rest of the JIRA issue form.                                                                                          
  9. Select Create at the bottom of the native JIRA page to create the defect in JIRA.  The Test Run page in qTest Manager is re-displayed and the JIRA window will automatically close.
  10. Now that you have linked a test to a new defect in JIRA, return to the TestPad in qTest Manager, complete the TestPad, and Save.  Close the TestPad and the JIRA ticket that you created is briefly displayed.                                                                         
  11. On the Test Run page, refresh your browser or click the Reload button, so that the recently executed log is displayed in the Execution History area of the page.
  12. To view the defect that was submitted during the execution, refer to the Execution History area of the Test Run page.  The red defect icon is displayed in two areas.
    1. The test log shows the defect occurred at the test run level.
    2. The test step log shows the specific step where the defect occurred.  

In the example below, the test run has been executed four times and the defect icon will display in both the test log and the test log details. Additionally, 'Defects (1)' displays in the tabs along the top as a visual indicator for the total number of defects associated with this Test Run.  Note, the defect icon displays in Test Run #3, and also in the 'Test Log 3 Details' section of the screen for Test Step #1. Therefore, the defect is associated with Test Step #1 for Test Run #3.

mceclip1.png

Link to an Existing Jira Defect

When executing a test, you may find a defect that was previously reported and already exists in JIRA.  In this case, it is useful to link to the existing defect in JIRA, rather than create a duplicate defect.  To link to an existing defect in JIRA, perform the following steps:

  1. Select the Defect (bug) icon for the step you failed. 
  2. In the Enter Defect ID field, enter the Defect ID of the existing defect you want to link.  
  3. Select the checkbox to ‘Include test execution details as defect’s comment’.
  4. Select the Link button to link the defect to the existing defect.
    link_defect_widget.png
    H
    INT: The defect is linked when the bug icon in qTest Manager is red.    
  5. Click the ID hyperlink to be redirected to the JIRA issue. Note, that a new comment in the JIRA issue shows the developer the steps to reproduce. 

Review JIRA Defect After Submission

The defect in JIRA will show qTest Manager test execution information, as well as other properties that you chose to auto-populate from Manager to the JIRA issue.  

JIRA_Defects_to_Requirements.gif

Within the JIRA issue, you will see the following:

  • test run properties
  • test run execution status and history
  • impacted user stories impacted by the defect

If your test case is associated with a JIRA requirement, the execution history will display and automatically link a JIRA defect issues to that requirement. 

 

Powered by Zendesk