...

• 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.

...

1. Open SOAtest and choose Parasoft> Test Configurations.
2. Right-click the Demo Configuration in the Built-in folder and choose Duplicate. This will create an editable duplicate in the User-defined test configuration folder.
3. Rename the duplicate test configuration and click the Execution tab. 
4. Click the Application Coverage tab and configure the following settings:
   • Enable the Enable Test Execution option. 
   • Enable the Collect application coverage option.
   • Specify the host or IP address of the AUT in the Coverage agent host field. The coverage agent should have been attached to the AUT in the previous step.
   • Specify the port number for the coverage agent. The default number is 8050.
   • If you are using multiple-user mode, specify an agent user ID, such as the current SOAtest username. This enables coverage to be associated with a specific user or client. Do not specify an agent user ID if the agent is not in multiple-user mode.
   • Enable the Report coverage agent connection failures as test failures option if you want test failures reported when the coverage agent connection fails. If the option is disabled, connection problems will only be reported to the console.
   • Enable the Retrieve coverage data and specify the where you want the store the dynamic coverage data in the Coverage data storage directory field. 
   • Enable Delete coverage data on retrieval option if you want the coverage data on the AUT to be deleted as soon as SOAtest retrieves it. We recommend enabling this option in order to prevent the taking up disk space on the coverage agent machine.
5. Click Apply the Test Configuration. to save the changes.
6. (Optional) Save the test configuration to your workspace. This step makes running the configuration on the SOAtest command line more convenient:
   1. Right-click the new
   Test Configuration
   1. test configuration and choose Export.
     
   1. Save the test configuration to the SOAtest workspace. 

In the next step, you will execute your tests using the new test configuration from the command line. But in order for DTP to associated the test results with the coverage information, you will need to create a properties file and specify the build ID used to create the static coverage file. The simplest way is to export the properties referenced by the SOAtest desktop.

...

Perform testing sessions, download the results, and mergee merge the coverage data, as described in steps 4-7 above. When downloading the results from CAM, ensure that the Session Tag field is completed with a tag unique to each user. We recommend that the session tag include the User ID.

Reviewing Application Coverage Results in DTP

In order to view coverage in the DTP dashboard, you will need to associate the coverage data sent to DTP with the filter.

1. Choose Report Center Settings from the DTP settings (gear icon) menu.
2. Click Filters and locate your DTP project. By default, a filter is created in DTP for each project. The filter has the same name of the project.
3. Click on the filter and verify that the appropriate run configurations have been added to the filter. A run configuration is a set of metadata about test and analysis executions that enable DTP to make the correct correlations for accurate reporting. If Jtest/dotTEST is configured to report to the project associated with the filter, then the run configurations will automatically be added to the filter by default.
4. In the Coverage Images section, rename one of the image indexes to Application Coverage  and choose the coverage image tag you specified from the Coverage Image drop-down menu. 
   Image Added
   You can include additional coverage images if you want to view all of your coverage data in one interface. 
   Changes are automatically saved.
5. Return to the DTP dashboard and add a coverage widget configured to show the Application Coverage coverage image.
   Image Added
6. Specify the filter and build ID in the dashboard settings and the widget will show your coverage data. 
   Image Added
   
7. You can click on the widget to view details in the Coverage Explorer view.
   Image Added