...
You can send test results analyzed by Selenic to Parasoft DTP, which aggregates, processes, and generates visualizations of the data. DTP applies advanced development and test analytics to the data it collects so that development managers and project members can assess the state of their software. See Viewing Results in DTP for information on viewing the data sent to DTP.Vimeo
| Scroll Ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
...
|
...
|
...
|
Run the selenic_analyzer.jar from the command line to send test results to DTP (see see Command Line).
Global Configuration
...
You can specify the following modes:
full | All source code from the specified scope is published to DTP. This is the default setting when the report.dtp.publish option is enabled. |
|---|---|
min | The minimal amount of source code is published. In most cases, auto-generated code and other source code without source control references will be published. |
off | Source code is not published to DTP. |
By default, Selenic will check for source files in the current directory. If your source files are stored in another directory, use the -source option when running the selenic_analyzer.jar file specify the location of your sources. See Command Line for usage details.
...
Each test execution is associated with a build ID, which is a unique identifier used to group a set of test runs. Refer to the DTP documentation for additional information about build IDs. By default, the project name and date of the execution are used as the build ID, but you can uncomment the build.id property and specify your own value:
...