Page History

...

1. Create work items in Polarion ALM that will be associated with tests executed by Parasoft C/C++test, dotTEST, or Jtest.
2. In your test file, add the Polarion test case or requirement IDs using the @test or @req annotation. See the C/C++test, dotTEST, or Jtest documentation for details on adding annotations.
   • Use the @test <Polarion unit test case ID> annotation in your tests to associate them with Polarion unit test cases. 
   • Use the @req <Polarion software/system requirement ID> annotation in your tests to associate them with Polarion software or system requirements. 
3. Execute your tests as part of the CI process. You can also manually execute the tests from the C/C++test desktop. 
4. As part of the test execution, C/C++test will tag the results with the filter and build IDs and send the data to DTP. You can verify the results in DTP by adding Test Widgets to your DTP dashboard and setting the filter and build ID. C/C++test developers can download the test execution data from DTP into their IDEs so that they can address any failed tests.

5. If you deployed the Sending Test Data to External Application flow (see Deploying the Sending Test Data to External Application Flow), then unit and functional testing results will automatically be sent to Polarion when Data Collector receives the data from the Parasoft tool.
   You can also manually send a POST request to the DTP REST API endpoint to send results from the DTP database to Polarion. Pass the DTP filter and build IDs as URL parameters in the API call:
   

   No Format
   httpscurl -X POST -u <username>:<password> "http://<host>:<port>/grs/api/v1.7/linkedApps/configurations/1/syncTestCases?filterId=<filterID>&buildId=<buildID>"

   The filter and build IDs are available in the Test Explorer URL:

   

6. DTP will locate the test results that match the filterId and buildId parameters and send the data to the Polarion unit test cases or requirements. You should expect the following response:

   • When DTP locates results with an @test <ID>, it will search for unit test cases with a matching ID in Polarion and update the item. No action will be taken if the unit test case IDs do not exist in Polarion.

   • When DTP locates results with an @req <ID>, it will search for requirements with a matching ID in Polarion and update associated children unit test cases. If no unit test cases exist for the requirement IDs, unit test cases will be created. Unit test cases will also be created if the requirement IDs are not found.  

   • An external-app-sync.log file will also be written to the the <DTP_INSTALL>/logs directory. This log file contains progress information about sending test results from DTP to Polarion. 

...