...
The Parasoft Findings plugin is designed to be used in a post test-execution build step that integrates functional and unit test reports generated by Parasoft tools into your Team City project. The task will collect test results from the Parasoft report XML files and display the number of passed/failed tests and result details. The results can also be displayed as trending data in a graph for a simple visualization. You can also view static analysis reports to identify code that does not comply with your static analysis rules.
The plugin can consume the following report types:
- Functional test reports generated by Parasoft SOAtest XML reports. 2020.1+.
- Static analysis, metrics analysis, and unit test reports generated by 2020.1+ versions of Parasoft Analyzers XML reports generated by Parasoft C/C++test, Jtest, and dotTEST tools.
Requirements
- TeamCity 20172020.1 .2 or later
Installing the Parasoft Findings Plugin
...
C/C++test reports for unit test results must be generated with the Overview of checked files and executed tests option enabled. You can enable this option on the command line by setting the report.contexts_details=true property in the settings file.
Viewing Static Analysis Reports
- Click the Duplicates tab of the build configuration to see duplicate violations.
- Click the Code Inspection tab of the build configuration to see Standard, Metric, and Flow violations.
If a report cannot be parsed, the build will fail. Details concerning the failure can be found on the Build Log tab.
It is recommended that you enable Delete all files in the checkout directory before the build in VCS settings for cleaner build logs.
If you are also using DTP, you may wish to set up a properties file containing your DTP URL, username, and password (note: with DTP 2023.1 or later, it is not necessary to provide DTP with a username and password to get rule documentation). Enter the location of that properties file in the Settings field of the build step you created as part of the Configuring the Plugin. Doing so will let you link rule documents being URL hosted by your DTP server to the TeamCity view. Recommended for use with DTP 2022.2 or later.
Note that the DTP URL must be entered using a domain name, as TeamCity does not currently support a <host_name>:<port> pattern. It may be necessary for you to set up a web server for DTP using a tool like Apache, Nginx, or something similar.
| Setting | Purpose |
|---|---|
dtp.url=HTTP|HTTPS://<domain_name> | Specifies the domain name for your DTP server. Must be entered using a domain name; TeamCity does not support a <hostname>:<port> pattern. Example: https://my.domain.com/dtp |
dtp.username=<username> | Specifies the username used to log into the DTP server. |
dtp.password=<password> | Specifies the password used to log into the DTP server. |
C/C++test Professional Report Settings
Reports for static analysis must be generated with the Add absolute file paths to XML data option enabled if you are using C/C++test Professional. You can enable this option on the command line by setting the report.location_details=true property in the settings file, which allows you to load source code on Duplicates tab.
Third-Party Acknowledgements
The Parasoft Findings Plugin for TeamCity uses the following third-party software:
Apache Commons Collections
This software is used under an Apache License 2.0 with this notice.
Apache Commons IO
This software is used under an Apache License 2.0 with this notice.
Apache HttpClient
This software is used under an Apache License 2.0 with this notice.
Apache HttpClient Fluent API
This software is used under an Apache License 2.0 with this notice.
Apache HttpClient Mime
This software is used under an Apache License 2.0 with this notice.
Apache XML RPC
This software is used under an Apache License 2.0.
Spring Core
This software is used under an Apache License 2.0 with this notice.
XML APIs
This software is used under an Apache License 2.0 with this notice.