...

The following requirements are only applicable if you are going to send test results to Jira:

• Tests executed by the following Parasoft tools are supported:
  • C/C++test Professional, dotTEST, or Jtest 10.4.3
  are supported
  • +
  • Selenic 2020.1 +
  • SOAtest 9.10.8 +
• Xray plug-in

Configuration

...

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.

Deploying the Sending Test Data to External Application Flow

This artifact sends test data to Jira when DTP Data Collector retrieves test results from a Parasoft tool. Before  This artifact ships with the Traceability Pack, which must be installed as described in Installing the Traceability Pack before deploying the flow, . You should also verify that the DTP Enterprise Pack connection is to DTP is configured  with with the host name of the server running DTP.  

...

1. Create tests and/or stories in Jira. The items will be associated with tests executed by Parasoft C/C++test, dotTEST, or Jtest. 
2. In your test file, add the Jira test or story IDs using the @test or @req annotation. See the C/C++test, dotTEST, or Jtest documentation for details on how to add annotations. 
   • Use the @test <Jira Test ID> annotation to associate tests with test executions in Jira.
   • Use the @req <Jira Story ID> annotation to associate tests with stories in Jira. 
3. Execute your tests as part of the CI process. You can also manually execute the tests from the IDE.
4. As part of the test execution, Parasoft test execution tools 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. 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 Jira 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 Jira. Pass the DTP filter and build IDs as URL parameters in the API call:

   https

   No Format
   curl -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 items in Jira.
   • When DTP locates results with an @test <ID>, it will search for and update tests with a matching ID in Jira. No action will be taken if the IDs do not exist in Jira.
   • When DTP locates results with an @req <ID>, it will search for Jira stories with a matching ID and add test executions to the story. If the ID does not exist, new test executions will be added to Jira. 
   • 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 Jira. 

After DTP processes the report and sends results to Jira, you should expect a response similar to the following:

...