...
| Option | Value | Description | ||
|---|---|---|---|---|
| -scope | <path> | A path to the scope configuration file. Required if the scope is other than the default; see Customizing Scope of Coverage. | ||
| -agentTimeout | <miliseconds> | Specifies the timeout for connection with the coverage agent. Adjust the timeout to your machine capabilities. The default value is 1500 ms.
| ||
| -port | <port number> | Specifies the port number when you start dottest_iismanager if the default port is unavailable. | ||
| -multiuser | Enables collecting coverage information for multiple users; see Collecting Coverage from Multiple Users. | |||
| -useSsl | Enables connecting via HTTPS; see Connecting with the the Coverage Agent via HTTPS. | |||
| -certificateHash | <SSL certificate hash> | Specifies the hash of the SSL certificate for the port that is used by the coverage agent; see Connecting with the Coverage Agent via HTTPS. | ||
| -certificatePath | <path> | Specifies the path to a PFX file that stores the SSL certificate; Connecting with the Coverage Agent via HTTPS. | ||
| -certificatePassword | <password> | Specifies the password to the SSL certificate stored in a PFX file; see Connecting with the Coverage Agent via HTTPS. | ||
| -displayappid | Prints the 'appid' of the dotTEST IIS Manager; see Connecting with the Coverage Agent via HTTPS. | |||
| -removeCertificate | Removes the SSL certificate when the port is manually unregistered with the -unregister switch; see Connecting with the Coverage Agent via HTTPS. | |||
| -skipvalidation | Enables using a self-signed SSL certificate; see Connecting with the Coverage Agent via HTTPS. |
Executing Tests to Collect Runtime Coverage
You can use SOAtest to run functional tests, as well as execute manual tests with Coverage Agent Manager (CAM). Refer to the SOAtest user guide or CAM documentation for details about performing test sessions.
When tests are being performed:
- SOAtest will collect runtime coverage, then merge it with static coverage, and upload the merged data to DTP.
- CAM will collect runtime coverage and test results, which must be manually downloaded. Next, you need to:
- manually upload test results to DTP; see Uploading Test Results to DTP.
- merge the runtime coverage with static coverage and upload the merged data to DTP; see Merging Static and Runtime Coverage and Uploading the Data to DTP.
...
- Go to Report Center in the DTP interface.
- Click the gear icon and choose Report Center Settings> Additional Settings> Report Center Administration> Tools> Data Collector Upload Form (requires admin permissions).
- Click Choose File and browse for the report.xml file you downloaded from CAM.
- Click the Upload button to upload the file to DTP.
If you use Jtest with dotTEST with SOAtest, test results are automatically sent to DTP during test execution. See the Application Coverage section in the SOAtest user guide at https://docs.parasoft.com.
| Anchor | ||||
|---|---|---|---|---|
|
If you use Jtest with dotTEST with CAM:
- 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).-publish: Sends the merged coverage to DTP.
Code Block dottestcli.exe -runtimeCoverage [path] -publish -staticCoverage [path]
If you use Jtest with dotTEST with SOAtest, static and dynamic coverage data are merged and sent to DTP during test execution. See the Application Coverage section in the SOAtest user guide at https://docs.parasoft.com.
...