Versions Compared

Old Version 7

changes.mady.by.user Hiromi Takahashi

Saved on

compared with

New Version 8

changes.mady.by.user Anna Stuchlik

Saved on

Key

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

...

  1. Ensure that Jtest is properly configured, including DTP, scope and authorship settings. See Connecting to DTP 1, Sending Results and Publishing Source Code to DTP, Configuration 1.
  2. Configure the following settings in the jtestcli.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.

  3. Run the Calculate Application Coverage test configuration using the following arguments:

    Code Block
    jtestcli -staticcoverage [path to static_coverage.xml file] -runtimecoverage [path/dir] -config "builtin://Calculate Application Coverage" -publish

    This ensures that Jtest has access to the runtime coverage data generated during test execution, as well as the static coverage data, which is required to fill the coverage.xml file with runtime coverage data.

...