Page History

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:

...

{
  "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"
    ]
}

Sending Results from a Specific DTP Project

If you are using the Sending Test Data to External System flow to forward unit and functional test results, data will be sent to Polarion for all DTP projects by default. As a result, work items will be updated to include the tests collected for any DTP project that contain annotations matching Polarion IDs. You can configure the flow, however, to only send data for a specific project. 

...

When the flow executes, only test results for the specified DTP project will be sent to Polarion. 

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. 

...