Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2020.1

...

You can associate multiple projects in DTP with a project in Polarion, but you cannot associate the same DTP project with more than one Polarion project.

Anchor
Enabling the Requirements Traceability Report
Enabling the Requirements Traceability Report
Enabling the Requirements Traceability Report

You can configure DTP to generate widgets and reports that help you demonstrate traceability between the requirements stored in Polarion and the test, static analysis, and build review data sent to DTP from Parasoft tools (C/C++test, dotTEST, Jtest, SOAtest). 

...

Deploying the External Application Traceability Report adds new widgets to Report Center, as well as a drill-down report. See Viewing the Traceability Report for instructions on adding the widgets and viewing the report.  

Anchor
Deploying the Sending Test Data to External Application Flow
Deploying the Sending Test Data to External Application Flow
Deploying the Sending Test Data to External Application Flow

This artifact sends test data to Polarion when DTP Data Collector retrieves test results from a Parasoft tool. This artifact ships with the Traceability Pack, which must be installed as described in Installing the Traceability Pack before deploying the flow.

  1. Open Extension Designer and click on the Services tab.
  2. Choose an existing service to deploy the artifact or create a new service in the DTP Workflows category. Refer to Working with Services for additional information on organizing services and artifacts.
  3. If you are adding the artifact to an existing service, add a new Flow tab (see Working with Flows) and choose Import> Library> Workflows> Traceability Pack> Sending Test Data to External Application  from the vertical ellipses menu.
  4. Click inside the Flow tab to drop the nodes into the service and click Deploy

Anchor
Advanced Configuration
Advanced Configuration
Advanced Configuration

You can modify the ExternalAppsSettings.properties configuration file located in the <DTP_DATA_DIR>/conf directory to change the default behavior of the integration. DTP's out-of-the-box integration with Polarion is configured to use default or commonly-used fields and work item types. If you customized your Polarion system, however, then you can configure the following settings to align data in DTP with your custom configuration.  

...

polarion.workItemType.requirementIds

Specifies a comma-separated list of Polarion work item types that should take the role of requirements in Parasoft. The work items are also used in the Traceability Report.

Choose Polarion Administration > Work Items > Types for the IDs in the Polarion UI to access the work item IDs in your Polarion system. 

Default:

polarion.workItemType.requirementIds=softwarerequirement,systemrequirement,requirement,userstory 

polarion.workItemType.testId

Specifies the Polarion work item type that should take the role of tests in Parasoft. 

Choose Polarion Administration > Work Items > Types for the IDs in the Polarion UI to access the work item IDs in your Polarion system.

Default:

polarion.workItemType.testId=unittestcase 

polarion.workItemType.issueSpecifies the type of work item to create in Polarion when creating new issues from the DTP Violation Explorer and Test Explorer. This enables you to associate custom issue trackers you may have configured in Polarion with work items created from DTP. 

By default, the property is not set. As a result, issue work items created in DTP are associated with issue work items in Polarion.

polarion.workItem.Type.taskSpecifies the type of work item to create in Polarion when creating new tasks from the DTP Violation Explorer and Test Explorer. This enables you to associate custom task trackers you may have configured in Polarion with work items created from DTP. 

By default, the property is not set. As a result, task work items created in DTP are associated with task work items in Polarion.

polarionIssueUrl

Specifies the URL template for linking work items created in the DTP Violation Explorer and Test Explorer to work items in Polarion.

Default:

polarionIssueUrl=<POLARION_URL>/polarion/redirect/project/<PROJECT>/workitem?id=<ID> 

polarion.hyperlinkRole

Specifies the role of hyperlinks as configured in your Polarion system. The hyperlink role is used when creating work items from the DTP Violations Explorer and Test Explorer.

Choose Polarion Administration > Enumerations > hyperlink-role-enum.xml in Polarion to access the hyperlink role.

Default:

polarion.hyperlinkRole=ref_ext

polarion.requirementStatus.verified

Specifies the relationship between the tests sent from DTP and the requirements in Polarion. Choose Polarion Administration > Enumerations > workitem-link-role-enum.xml in Polarion to view the current relationship configurations.

Default:

polarion.requirementStatus.verified=verifies 

Anchor
Usage
Usage
Usage

After configuring the integration with Polarion, developers, testers, and other users can leverage the functionality enabled by the integration.

Anchor
Manually Creating Defects and Issues in Polarion ALM
Manually Creating Defects and Issues in Polarion ALM
Manually Creating Defects and Issues in Polarion ALM 

The Test Explorer and Violations Explorer views enable you to create issues and defects for any test and violation, respectively, regardless of status. Refer to the following sections for details on creating Polarion assets in explorer views:

Anchor
Sending Test Data to Polarion
Sending Test Data to Polarion
Sending Test Data to Polarion

The following diagram shows how you could implement an automated infrastructure for integrating Parasoft DTP and Parasoft test execution tools into your Polarion ALM environment:

...

Code Block
languagejs
{
  "createdTestSession": "DTPP-521",
    "created": [
        "DTPP-519, testName = testBagSumAdd"
    ],
    "updated": [
        "DTPP-519, testName = testBagSumAdd",
        "DTPP-518, testName = testBagSimpleAdd"
    ],
    "ignored": [
        "MAGD-567, testName = testBagNegate",
        "QAP-512, testName = testTryThis3",
        "QAP-512, testName = testTryThis4",
        "MAGD-567, testName = testBagMultiply"
    ]
}

Anchor
Viewing Results in Polarion
Viewing Results in Polarion
Viewing Results in Polarion

After successfully sending the test data to Polarion, you will be able to view results in Polarion. 

...

 You can drill down into Polarion reports to view additional details about the tests, including authorship, location, and execution time. Refer to the Polarion documentation for details about understanding reports in Polarion.

Anchor
Viewing the Traceability Report
Viewing the Traceability Report
Viewing the Traceability Report

If the External Application Traceability Report has been deployed to your system (see Enabling the Requirements Traceability Report), you can add widgets to your dashboard to monitor traceability from requirements to tests, static analysis, code reviews for your project. The widgets also drill down to a report that includes additional details. 

...

Requirements Implementation by Reviews

Anchor
Understanding the Requirement Traceability Report
Understanding the Requirement Traceability Report
Understanding the Requirement Traceability Report

The report lists the Polarion project requirements and data associated with them. 

...