If a test run fails or requires additional development effort, the tester can log a defect. You have various ways you can submit a defect from the Test Execution area:
- To submit the defect DURING test execution, you can do so from the Quick Run or TestPad window. For more details on Quick Run and TestPad, check out this article: Executing Test Runs
- To submit a defect AFTER a test run was already executed, this allows you to submit the defect from the Test Log in Execution History.
This article shows how to submit defects to qTest Manager as well as JIRA. If you use another tool to track defects, check out Submitting Defects sections within each Integration Guide.
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.
Submit Defect After 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.
- Select Bug icon in a Test Log in Execution History section to submit/link Defects to an entire Test Log
- Alternatively, select Bug icon in a Test Log Details to submit/link Defects to individual Test Steps of an executed Test Log
- Click either Bug icon will open a pop-up to submit/link Defects
- Click New to submit a Defect linked to the Test Log.
- If you want to link to an existing defect, please enter the Defect ID to link to the Test Log.
- Click Delete icon to remove a linked Defect out of the Test Log.
Autopopulating Defect Data
Defect's Description will only auto-fill with Test Steps Description when you submit Defects linked to individual Test Steps.
Using qTest Manager Defects
Submit a New Defect in Manager
- To submit a defect, click the Bug icon for the test step you failed.
- To log a new defect, select the ‘Include all test step details’ checkbox in the top left of the pop-up window.
- We recommend selecting this checkbox so that when a developer reviews this defect, he will understand the steps to reproduce it.
- Click the New button. The New Defect page is displayed.
- In the Summary field, enter the name of the defect. Then, fill in the other information on the screen. The fields on the page are created in Field Settings and determined by the user. If you selected the ‘Include all test step details’ checkbox in step 9, all steps leading up to where the test failed are copied from the test run to the Description area of the New Defect page. If you wish, you can add an attachment to take a screenshot of the error and upload it in the Attachment area of the page.
- Click the Save & Close button to save the defect and close the screen. The Test Pad or Quick Run window will be redisplayed.
- To verify the defect has been created, move the cursor to the step that failed and then click the Bug icon. The ID for the defect, summary of the defect, and defect status (‘New’) are displayed.
- In the Mark test run’s Status as field on the TestPad, click the down arrow and select the option to indicate the test run has failed.
- Click the Save button to save your changes. Then, close the TestPad.
Link to an Existing Defect in Manager
- Enter the Defect ID of the existing defect in the Enter Defect ID field.
- On the pop-up screen, click the Link button to link the defect to an existing defect.
- At the top of the TestPad, select the status of the test run.
- Click the Save button and then close the Test Pad. Click the Reload button to refresh the page and then navigate to the Test Run that was just executed.
- To view the defect that was linked to the test run, click 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, the Linked Defects area of the Test Run page will display the defect’s up-to-date status. The Defect Summary of the test suite, cycle, and release will also roll up defect information related to any of its associated test runs.
For advanced reporting, use qTest Insights to gain more defect visibility.
Using JIRA Defect Integration
The browser plugin allows for a native submission experience into JIRA so that you don't have to constantly map system fields. This plugin requires no settings and works immediately upon installation.
Submit a New Defect (JIRA Users)
- Click the Bug icon for the step you failed.
- Click the New button. The Select a Defect Type pop-up window is displayed.
- Leave the Defect Project field blank.
HINT: 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.
- In the Defect Type field, from the drop-down list select the JIRA project and JIRA issue type that represents the defect (e.g., bug, task, etc.) to create in JIRA. Then, click the OK button.
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.
- Fill in all necessary details with regard to how your team fills out 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.
- Click the Create button 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.
- Now that you have linked a test to a new defect in JIRA, return to the TestPad in qTest Manager, complete the TestPad, and click the Save button in the TestPad to save the results. Close the TestPad. The JIRA ticket that was created is briefly displayed.
- 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.
- 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.
- The test log shows the defect occurred at the test run level.
- The test step log shows the specific step where the defect occurred.
In the screen shown below, the test run has been executed twice and a defect occurred in both the test log and the test step log. The second time the test was executed, the defect occurred at step 4.
Link to an Existing JIRA Defect
When executing a test, in some cases you may find a defect that was previously reported and already exists in JIRA. In these cases, it is useful to link to the existing defect in JIRA, rather than create a duplicate of the defect. To link to an existing defect in JIRA, perform the following steps.
- Click the Bug icon for the step you failed. The following pop-up window is displayed.
- In the Enter Defect ID field, enter the Defect ID of the existing defect you want to link to.
- In the pop-up window, click the checkbox to ‘Include test execution details as defect’s comment’.
- Click the Link button to link the defect to the existing defect.
HINT: You can see the defect is now linked because the bug icon in qTest Manager is red.
- 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 you decided to auto populate from Manager to the JIRA issue.
Within the JIRA issue, you will see the test run properties, test run execution status and history, as well as any impacted user stories impacted by the defect.
If your test case was associated with a JIRA requirement, we will show the execution history and automatically link a JIRA defect issues to that requirement.