...
Table of Contents | ||
---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Xray
The following diagram shows how you could implement an automated infrastructure for integrating Parasoft DTP and Parasoft test execution tools into your Jira environment:
...
- Create tests and/or stories in Jira. The items will be associated with tests executed by Parasoft C/C++test, dotTEST, or Jtest.
- 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. - The Jira work item ID is available in several Jira interfaces, such as the URL:
- Use the
- Execute your tests as part of the CI process. You can also manually execute the tests from the IDE.
- 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.
If you deployed the Sending Test Data to External System flow (see Deploying the Sending Test Data to External System Flow), then unit and functional testing results will automatically be sent to Jira when Data Collector receives the data from the Parasoft tool. By default, the flow forwards unit and functional test results that were received by Data Collector for any project, but you can configure the flow to only send data for a specific project (see Sending Results from a Specific DTP Project). You can also manually send a POST request to the DTP REST API endpoint in order to send results from the DTP database to Jira (see Manually Sending a POST Request to the DTP REST API Endpoint).
- DTP will locate the test results that match the
filterId
andbuildId
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
<DTP_INSTALL>/logs
directory. This log file contains progress information about sending test results from DTP to Jira.
- When DTP locates results with an
...
No Format |
---|
{ "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" ] } |
Manually Sending a POST Request to the DTP REST API Endpoint
The Sending Test Data to External System flow shipped with the Traceability Pack will automatically send data from DTP to Jira when new results are collected in DTP (see Deploying the Sending Test Data to External System Flow). Alternatively, you can send a POST request to the DTP REST API endpoint to start this action (refer to syncTestCases Endpoint Reference for details about the endpoint).
...
Refer to the Jira documentation for information about configuring versions.
syncTestCases Endpoint Reference
The syncTestCases
endpoint sends test data that has been reported to DTP to the integrated ALM system.
...
Scroll Table Layout | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Parameter | Value | Description | Required |
---|---|---|---|
filterId | integer | Specifies the filter ID containing the test data. The filter ID is an integer value and should not be confused with the filter name. | Required |
buildId | string | Specifies the build ID containing the test data. | Required |
fixVersions | comma-separated list of string | Specifies a value for populating the Fix Version field in Jira. The Fix Version field is a necessary field for using Jira's traceability reports. | Optional |
groupResultsBySOAtestTST | boolean | Setting to Setting to Default is See Changing Test Granularity for SOAtest Results for additional information. | Optional |
Changing Test Granularity for SOAtest Results
SOAtest offers the flexibility to implement several testing strategies, such as:
...
If you deployed the Sending Test Data to External Systems flow, you can add the parameter to the linkedApps - syncTestCases node to enable grouping by .tst file:
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 Jira 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 Jira 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 Jira.
Viewing Results in Jira and Xray
You will be able to view results in Jira after sending the test data. The following image shows a Jira story that contains several tests.
...