...
- Choose Report Center Settings from the settings (gear icon) drop-down menu.
- Choose External System System, click Edit Settings, and choose Azure DevOps from the System type drop-down menu.
- Enable the Enabled option.
- Enter the a name for the server in the Name field. The name is required but does not affect the connection settings or render in any other interfaces.
- Enter the URL of your Azure DevOps system in the Application URL field. Must include your Azure DevOps collection name.
- The Display URL field defines the URL which is displayed in Parasoft DTP pages when links to your Azure DevOps system are presented in a web browser. Typically, this should be the same as the above Application URL field. However, it might be different, for example, when you work in a reverse proxy environment and links to Azure DevOps from the user's local web browser with Parasoft DTP are different than from the Parasoft DTP server. (e.g., https://dev.azure.com/{yourorganization})
- Enter your username and Azure DevOps API token in the appropriate fields. (See: Generate Azure DevOps Token below.) The login must have sufficient privileges to create Azure DevOps issues in the projects specified in the Project Associations section.
- Click Test Connection to verify your settings and click SaveConfirm.
Generate Azure DevOps Token
Sign in to your organization in Azure DevOps (
https://dev.azure.com/{yourorganization})From your home page, open your user settings, and then select Personal access tokens.
- Select + New Token.
- Name your token, select the organization where you want to use the token, and then choose a lifespan for your token.
Select the scopes for this token to authorize for your specific tasks.
- Under Scopes, select Custom defined.
- Click on the Show all scopes.
- Select Test Management and enable Read & write.
- Select Tokens and check enable Read & manage.
- Select Work items and check enable Read, write, & manage.
- Click Save.
- When done, make sure to copy the token. For your security, it won't be shown again. Use this token as your password.
...
- Choose Extension Designer from the settings menu (gear icon).
Enabling the Requirements Traceability Report
- Click the Configuration tab to open Artifact Manager.
- Click Upload Artifact and browse for the traceability-pack-<version>.zip archive (also see Downloading and Installing Artifacts).
- Click Install and a collection of assets and configuration files for enabling traceability will be installed.
Requirements
The following requirements are only applicable if you are going to send test results to Azure DevOps.
Advanced Configuration
You can modify the ExternalSystemSettings.properties configuration file located in the <DTP_DATA_DIR>/conf directory to change the default behavior of the integration. DTP's out-of-the-box integration with Azure DevOps is configured to use default or commonly-used fields and work item types. If you customized your Azure DevOps system, however, then you can configure the following settings to align data in DTP with your custom configuration.
| azuredevops.workItem.url | Specifies the URL template to the specific item in Azure DevOps. Default:
|
|---|---|
azuredevops.workItemType.requirements | Specifies the list of work item types in Azure DevOps treated as requirements in DTP Traceability reports, Parasoft C/C++ and SOAtest Requirements Views, and Test Case Synchronization processes. Separate names with a semi-colon ( ; ). Default:
|
| Note |
|---|
If you upgraded your Parasoft DTP installation from a version prior to 2021.2, these Azure DevOps parameters might be missing in your ExternalSystemSettings.properties file. In this case, they take the default values shown in the table above. To change these parameters, be sure to add them to your ExternalSystemSettings.properties file. |
Requirements
The following requirements are only applicable if you are going to send test results to Azure DevOps.
- Tests executed by the following Tests executed by the following Parasoft tools are supported:
- C/C++test Professional, dotTEST, or Jtest 10.4.3 +
- Selenic 2020.1 +
- SOAtest 9.10.8 +
- You should have already created requirements in Azure DevOps.
...
The Test Explorer and Violations Explorer views enable you to create issues and defects for any test and violation, respectively, regardless of status. Refer to the following sections for details on creating Azure DevOps assets in explorer views:
- See "Creating an Issue in a Third-party System for " on the Violations Explorer page for instructions on how to manually create work items in Azure DevOps from the Violations Explorer view.
- See "Creating an Issue in a Third-party System" on the Test Explorer page for instructions on how to manually create work items in Azure DevOps from the Test Explorer view.
...