...
- Ensure that dotTEST is properly configured, including DTP, scope and authorship settings. See Connecting to DTP 1, Sending Results and Publishing Source Code to DTP, Configuration.
- Configure the following settings in the dottestcli.properties file in order to properly merge coverage data:
-report.coverage.images- Specifies a set of tags that are used to create coverage images in DTP. A coverage image is a unique identifier for aggregating coverage data from runs with the same build ID. DTP supports up to three coverage images per report.
-session.tag- Specifies a unique identifier for the test run and is used to distinguish different runs on the same build.
-build.id- Specifies a build identifier used to label results. It may be unique for each build, but it may also label several test sessions executed during a specified build. Copy the runtime coverage and static coverage files to the same machine and run
dottestcliwith the following switches:-runtimeCoverage: Specifies the path to runtime coverage that you download with CAM (see Coverage Agent Manager (CAM) section of the DTP documentation for details). You can provide a path to an individual .data file with coverage information from one testing session, or a path to a folder that contains many .data files from multiple testing sessions.-staticCoverage: Specifies the path to the static coverage file (see Generating the Static Coverage File).
Code Block dottestcli.exe -runtimeCoverage [path] -report [path] -publish -settings [path] -out [path] -staticCoverage [path]
...