Codebeamer ALM is a popular browser-based platform for managing requirements. Meanwhile, Parasoft testing tools and DTP provide comprehensive automated testing tools that find quality problems and run tests in the software project. You can enhance your project workflow by integrating Codebeamer ALM with Parasoft DTP, which strengthens traceability between two pivotal system elements:
- Codebeamer ALM, which is responsible for the definition of requirements, defects, and tests.
- Parasoft testing tools, which execute automated tests and find defects and violations in your software, plus Parasoft DTP, which is a reporting and analytics dashboard.
Integrating your Parasoft tools with Codebeamer ALM provides the following functionality:
Creating defects in Codebeamer ALM from Parasoft DTP Violations Explorer and Test Explorer views
When Parasoft testing tools detect a static analysis violation or when an automated test failure is reported in DTP, you can effortlessly create a defect report in the integrated Codebeamer ALM directly from the Parasoft DTP interface. See Manually Creating Bugs and Tasks in Codebeamer ALM.
Sending Parasoft tests results to Codebeamer ALM requirements and test definitions
Your software requirements are defined in Codebeamer ALM, while Parasoft tools and DTP are used to test the implementation of these requirements. You can track traceability between these requirements in Codebeamer ALM and test results in Parasoft DTP using traceability reports in Codebeamer ALM by sending test results from Parasoft DTP to Codebeamer ALM. See Sending Test Data to Codebeamer and Viewing Results.
Monitoring Codebeamer ALM Requirements Traceability to Test Results in Parasoft DTP Reports
This use case is similar the previous functionality, where the aim is to monitor traceability from Codebeamer ALM requirements to Parasoft test results. However, the difference lies in the source of the reports. While the previous functionality facilitated reports in Codebeamer ALM, this one utilizes reports in Parasoft DTP. See Parasoft to Codebeamer Traceability Reports.
Configuration
Before you can take advantage of these features, some configuration is required. See Configuring Integration with Codebeamer.
In addition, if you intend to use the Monitoring Codebeamer ALM Requirements Traceability to Test Results in Parasoft DTP Reports functionality mentioned above, there are some additional configurations required. See Configuring Parasoft to Codebeamer Traceability.
Note for Upgrades
If you upgrade DTP from a version prior to 2023.2 and intend to integrate with a newer version of Codebeamer (for example, Codebeamer 22), you will need to edit your ExternalSystemSettings.properties file, found in the <DTP_DATA_DIR>/conf/ directory. Open it and add the new property codeBeamer.restApi.path and set it to the correct prefix path for your installation of Codebeamer. The typical prefix path for newer versions of Codebeamer is /rest. This property has not been added to your ExternalSystemSettings.properties file as part of your upgrade.
Older versions of Codebeamer used the default prefix path of /cb/rest and, if the codeBeamer.restApi.path property is not set in your ExternalSystemSettings.properties file, DTP will continue to use that older default.
In addition, it is recommended that you review the codeBeamerIssueUrl property, which might be set to the older default of <CODEBEAMER_URL>/cb/issue/<ID>. Determine if this is still accurate for your installation of Codebeamer, particularly the /cb prefix.
For more information about this property and configuring ExternalSystemSettings.properties, see Advanced Configuration.
