Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can configure a Qualitia project to create a defect for a test case iteration report. You need to integrate a Qualitia project with one of Qualitia Automation Studio supports integration with the following defect management systems: 

  • Jira

  • TFS/Azure

DevOps.Quaitia automatically logs the defects
  • DeveOps

You can configure a QAS project to log a defect in the defect management system for a test case iteration report whose executions status is Defect. However, in certain conditions where auto-logging of defects are not possible, then you need to log the defects manually.For more information, refer to Conditions for Auto-Logging of Defects.execution.


Info

When a defect is logged automatically or manually for a test case iteration, Qualitia does not verify whether the defect for the test case that iteration is already created. 

Configuring a Qualitia

Integrating a QAS Project with a Defect Management System Project

You can integrate a Qualitia QAS project to a with any Jira or TFS/DevOps project for managing defectsdefect management. 

You can use the Auto-Mode option to enable or disable auto-logging of defects. You can log defects manually even if the auto-log mode is disabled.

To configure a

If you enable the Auto-Log mode, then after the suite execution, QAS creates defects automatically in the mapped Jira/TFS project for the test case iterations whose suite execution status is defectElse, after the suite execution, you need to manually create a defect in the test case iteration report.

To integrate a Qualitia Project with a defect management system:

  1. Do one of the following to access the Project Settings dialog box.
    1. Go to Admin >Project, under the Configuration column, click Configure next to a project that you want to integrate with a defect management system.
    2. Go to Settings > Project Settings. 
      A list of existing Qualitia projects appear.
  2. Click the Defects tab.
  3. Do one of the following:
    • Click the Jira tab to integrate with a Jira for logging the defectsproject.
    • Click the TFS tab to integrate with a TFS/Azure DevOps project for logging the defects.  
  4. Perform this step only if you want to integrate with a Jira project.
    • Jira URL: Lets you specify  Specify the Jira Server URL to which you want to connect for logging the defects.
    • User Id: Lets you specify Specify your Jira User Id to connect with the Jira Project
    • Password: Lets you specify  Specify your Jira password to authenticate the Jira Project.
      Note: If you do not enter a Jira User id and password, then Qualitia uses the credentials of the first user who had configured the Qualitia project with the selected Jira Project.
    • Connect: Click to get connect to the available Jira projectsserver.
    • Jira Project: Lets you select  Select the Jira project from the drop-down list to which that you want to integrate the current project defectsuse to log defects for the selected Qualitia project.
  5. Perform this step only if you want to integrate with a TFS/ Azure DevOps project. 
    • Server URL: Lets you specify  Specify the TFS/Azure DevOps URL.

    • PAT: Lets you specify  Specify the unique Personal Access Token (PAT) provided by Microsoft Azure DevOps.

    • Get Projects: Click this button to display the list of all the available projects in TFS/Azure DevOps Server

    • Project: Lets you select a project to which  Select the project that you want to integrateuse to log defects for the selected Qualitia project.

  6. Enable Auto-Log Mode to to allow Qualitia to auto-log the defects for the test case iterations with execution status “Defect”.
  7. Under Mandatory Defects Fields, select or enter  enter the default values in for the mandatory fields that are automatically displayed, which are defined in the defect management system that must be used to auto-log the defects.
    For example, if you are integrating with a your Jira project , which defines that severity and priority are mandatory, then Severity and Priority for the defects as mandatory fields, then these two fields are displayed on this dialog box displays these two fields. You need to must enter the default values in for these two fields to be used while auto-logging the defects.
    Note: Qualitia supports only basic data types such as Number and List/Option, for integration with Defect Management Systems (Jira and TFS). Qualitia does not support complex data types such as custom user-defined data types, nested objects, and dates.
  8. Click Save to save the settings.

Conditions for Auto-Logging of Defects

The auto-logging of defects occurs only for the test case iteration reports whose execution status is Defect. 

For auto-logging of defects, you must ensure to do the following: 

  • Enable the Auto-Log mode in the Defects tab of Project Settings dialog box.
  • Ensure the test suite execution results are pushed to Real Time reporting portal. For more information, refer to Pre-Requisites for Real Time Reporting Portal.

Logging a Manual Defect from a Test Case Iteration Report

The following table shows the scenarios where logging of defects manually can be used as an alternative to auto-logging of defects. 

Scenarios and ConditionsAuto-Logging of DefectManual Logging of DefectsTest Case Iteration Execution StatusOnly DefectPass, Fail, and DefectAuto-mode is disabled ( A setting in the Defects tab of Project Dialog Box that enables auto-logging of defects)NoYesReal-time Reporting Fails to display test suite executionsNo

Yes

After uploading the report in Reporting Portal

Offline Package execution is not configured with Qualitia Server or both lost their connection during the executionNo

Yes

After uploading the report in Reporting Portal

Test cases executed through TFS/Azure DevOpsNoYesTo log a manual defect in the integrated defect management system

Replacing the Mapping for a Qualitia Project with another Defect Management Systems Project

Info
titleImportant
You cannot directly change the settings in the Defect tab of Project Settings if you want to replace the mapping of a Qualitia Project to another Jira/TFS project. 

Perform the following steps to change the defect management systems project.

To replace the mapping for a Qualitia project with another defects management system project:

  1. Do one of the following:

    • Go to Admin Project, under the Configuration column, click Configure next to a project.

    • Go to Settings > Project Settings.

  2. Click the Defects tab.

  3. Select the Target Defect Management System to None.

  4. Click Ok.

You can now integrate the Qualitia project with another defect management system project. For more information, refer to Integrating a Qualitia Project with a Defect Management System Project.

Logging a Defect Manually from a Test Case Iteration Report

Qualitia does not support auto-logging of defects in the following scenarios:

  • Test case iteration, which are defects whose execution status is Pass, Fail, or Not Executed

  • The test case iteration execution status is Defect, but the Auto-Logging Mode was disabled at the time of the suite execution.

  • The Test Case Suite Execution report did not display in the Real Time Reporting portal.
  • The test case was executed through a TFS/Azure DevOps pipeline.

In such scenarios, you can log defects manually from the test case iteration report. 

Info

If the Test Case Suite Execution did not display in the Real Time Reporting portal, you need to upload in the Real Time Reporting Portal. For more information, refer to Uploading a Test Suite Execution Summary Report.

You cannot log defects for the test case iterations whose execution status is "Not Executed".

To log a defect manually:

  1. Login to Reports and Dashboard Portal.
  2. Click Real Time Reporting Portal.
  3. From the Suites of Suites screen, open the test execution in which for which you want to create a defect.
  4. From the Test Suite Execution Summary Report, open the Test case, and then click the test case iteration for which you want to create a defect.
    Note: The status of test case iteration must not be Not Executed.

  5. Click the three dots menu present on the right side of the page and select , and depending on the defect management system you use, click Log JIRA defect or  or Log TFS defect.
    (Depending on the Defect management system you have integrated with Qualitia Project) 

  6. Do the following in the order listed:

    1. The Defect Title is automatically generated in the format as Suite Name – Test Case Name – Test Case Iteration Number.
      You can edit this field.with details of the test case iteration number and if space is left, it will contain the Scenario name and Test Suite name.
      Note: You can edit the Defect Title, but you cannot add more than 255 characters including blank spaces in it. 
    2. Enter the required information associated with the defect, in Defect Description.
      The default content for this field automatically displays environment details such as browser name, which you can edit.

    3. Under Mandatory Defects Fields, select or enter Enter the default values for the mandatory fields.As per the settings defined in the project of the selected Defect Management System, the mandatory fields are displayed automatically.  
      For example, if a Jira project to which you want to integrate defines that severity and priority fields are mandatory, then this dialog box displays severity and priority under Mandatory Fields.
  7. Click Submit.Click Create
    A notification message with the defect Id and its URL is displayed.
  8. Click the Defect URL to view this defect in the associated configured defect management system. 
    The defect created in the associated defect management system project shows logged defect contains the link to the corresponding Qualitia test case iteration of the test suitereport.

Viewing Defects in Real Time Reporting Portal 

Open the test suite execution report in which a defect is created automatically or manually.

Under the Status column, upon hovering on a  a bug icon indicates the associated test case iteration report has a defect logged with the integrated defect management system. Upon hovering on the icon, all the associated defect Ids IDs along with their links are displayed. Also, you can know whether the defect is automatically created or not.

Viewing Defects in the Selected Defects Management System

The issue created in the selected defect management system contains the following details: 

  • For defects that are automatically logged, the descriptions contain the details such as Machine Name, Operating system used, and Browser name along with its version.
  • When a defect is created, its default name is generated as Test Case Iteration number - Test Case name - Suite Name.
  • After a defect is created, the defect contains a link to view the test case iteration report in Real Time Reporting Portal

     You can also identify whether the defects were created automatically or manually.

    On this Page:

    Table of Contents