Versions Compared

Key

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

...

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

If you are using the Jira Xray traceability report (in addition to, or instead of, the Parasoft traceability report), the test information sent to Jira must include the Fix Version field. By default, the DTP API does not populate the Fix Version field when it creates test execution entities in Jira,
but you can add the fixVersionfixVersions parameter to your API and specify one or more values to populate the field:

No Format
curl -X POST "https://<host>:<port>/grs/api/v1.7/linkedApps/configurations/1/syncTestCases?filterId=<filterID>&buildId=<buildID>&fixVersionfixVersions=<version1>,<version2>"

You must also first enable the Version field in your Jira project to use the fixVersion fixVersions parameter. The value of the parameter must match the version specified in your Jira project. In the following example, tests would be updated for fixVersionfixVersions=1.0

Refer to the Jira documentation for information about configuring versions.

...

ParameterValueDescriptionRequired
filterId integerSpecifies 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 stringSpecifies the build ID containing the test data.Required
fixVersionfixVersions comma-separated list of stringSpecifies 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 true groups SOAtest results by .tst file. As a result, one .tst file will be associated with one Xray test.

Setting to false associates each test step within a SOAtest .tst with an Xray test.

Default is false 

See Changing Test Granularity for SOAtest Results for additional information. 

Optional

...