In this section:
To enable sending results and publishing source code to DTP, you need to ensure that the connection to your DTP server is properly configured, see Connecting to DTP. |
Verify that the source-related settings are properly configured to ensure that data is presented in the drill-down reports consistently. |
You can enable sending results to DTP by the report.dtp.publish property to true:
report.dtp.publish=true |
Alternatively, you can use the -publish command line switch:
dottestcli.exe -solution "C:\Devel\FooSolution\FooSolution.sln" -config "builtin://Demo" -publish |
You can associate results sent to DTP with a specific DTP project by configuring the dtp.project property. For example, the following configuration will associate the results published to DTP with the "extensions" project:
dtp.project=extensions |
By default, tested sources are sent to DTP when reporting to DTP is enabled. This enables DTP to present source code associated with findings.
You can use the report.dtp.publish.src property to disable the publishing of source code, restrict the depth of source code publishing, or enable source code publishing when sending reports to DTP is disabled.
The report.dtp.publish.src property can be set to one of the following values:
off: Source code is not published to DTP.min: Publishes the minimal part of sources. Only the source code that has no reference to source control is published.full: Publishes all sources associated with the specified scope. This is the default setting.See Report Settings for details.
See the "DTP User Guide" for additional information about viewing source code in DTP.
dotTEST needs to execute to send data to DTP, but you may want to send publish sources to DTP without running analysis.
<INSTALL_DIR>\configs\user; see Configuring Test Configurations for details.report.dtp.publish.src property.