If Parasoft code analysis and test execution tools connected to DTP are configured to publish source code, then copies of the analyzed files are stored in DTP's database. DTP will display the correct version of a file when you view the sources in an explorer view. Parasoft tools can also send copies of source files to DTP without analyzing code. See "Publishing Sources to DTP Server" in the C/C++test, Jtest, or dotTEST documentation.
- Configure the Parasoft tool to publish source files to DTP (refer to your tool's documentation for details).
- Run the tool.
- The sources will appear in an explorer view.
Benefits of Publishing Source Code from Parasoft Tools
- Enables fast access to source files without additional configuration in DTP Server.
- Supports source files that are not stored under source control (such as auto-generated files during build).
- Allows you to display source files stored under source control systems that are not natively by DTP.
- Provides support for source files that are modified, moved, or copied during build (that is, files that get disconnected from original source control system).
Additional Considerations
- All analyzed versions of source files are stored at DTP Server.
Deleting Previously Published Source Code
Delete previously published source code by removing the content in the <DTP_DATA_DIR>/data/_DEFAULT_/dc/sources directory.
When code analysis from Parasoft tools is re-executed (with publishing source code enabled), the file versions will be recreated.
Static analysis violations, unit tests, or coverage data that were reported for previously sent versions of files that are not re-published will no longer be displayed in an explorer view. If one of the other source code publishing methods is used, though, DTP may fallback to another version.
