Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Generating the static coverage file. When you have access to the application source code, the static coverage file should be generated by Jtest or dotTEST in .xml or .data format as this method comes with several advantages over the alternative. You can also generate the static coverage file by analyzing the application binaries using the coverage tool shipped with SOAtest when you do not have access to the application source code. See Generating the Static Coverage File below for more information.
  2. Attaching the coverage agent to the application under test (AUT). The coverage agent ships with SOAtest and allows you to monitor the code being executed when the AUT is running.
  3. Configuring SOAtest to connect to the coverage agent and collect runtime coverage and upload the data to DTP.
  4. Executing tests with SOAtest as part of an automated process.
  5. Reviewing the application coverage on DTP in the Coverage Explorer.
Note

Coverage reports produced by Starting with SOAtest 2023.1, coverage reports that are uploaded to DTP need to be sent to DTP 2023.1 or later. Earlier versions of DTP will not properly process coverage reports produced by SOAtest 2023.1 and newer versions.

Anchor
GeneratingStaticCoverage
GeneratingStaticCoverage
Generating the Static Coverage File

...