Root nodes

Edit online

The first level of the navigation tree contains the aggregate report and individual execution runs:

Final report

Select this node to view the aggregate map coverage results rolled up across all combined coverage runs. Hover over this node to view a tooltip that shows the total elapsed time in seconds and the overall final status of the aggregate run.

The tooltip uses the following syntax:

Coverage finished in [total_elapsed_time] seconds
Overall Status: [status]
Top map: [status]
Functional map: [status]
Run map: [status]

Example:

Coverage finished in 15.342 seconds.
Overall Status: Partially covered
Top map: Covered
Functional map: Partially covered
Run map: Not covered

In this example:

  • Coverage finished in 15.342 seconds - This line displays the total elapsed execution time in seconds for the combined coverage runs. In this example, the coverage analysis finishes in 15.342 seconds.
  • Overall Status: Partially covered - This line displays the consolidated coverage status for the entire map hierarchy across all active runs. The status can be Covered, Partially covered, or Not covered. In this example, the status is Partially covered, which indicates some map rules execute during the test runs, but at least one map rule does not execute.
  • Top map: Covered - This line displays the aggregated coverage status for the map rules that are directly associated with the output cards of the top-level executable map. In this example, the status is Covered, which indicates that the test runs exercise all top-level map rules at least once.
  • Functional map: Partially covered - This line displays the aggregated coverage status for all map rules that nested functional maps contain. In this example, the status is Partially covered, which indicates that the test runs exercise some functional map rules, but some functional map rules do not execute.
  • Run map: Not covered - This line displays the aggregated coverage status for all run map rules that the RUN function calls. In this example, the status is Not covered, which indicates that no run map rules execute during any of the test runs.

Specific coverage ID

This node shows the unique identifier of an executed coverage run, such as Default or GoodAudit. Select this node to filter the rules table to show only the results for that specific coverage run. Hover over this node to view a tooltip that shows the total elapsed time in seconds and the final status of this specific coverage run.

The tooltip uses the following syntax:

Coverage finished in [total_elapsed_time] seconds
Overall Status: [status]
Top map: [status]
Functional map: [status]
Run map: [status]

Example:

Coverage finished in 2.456 seconds.
Overall Status: covered
Top map: Covered
Functional map: Partially covered
Run map: Not covered

In this example:

  • Coverage finished in 2.456 seconds - This line displays the execution duration in seconds for this specific coverage run. In this example, the value of 2.456 seconds indicates that this specific coverage run finished in 2.456 seconds.
  • Status: Covered - This line displays the final coverage status for this specific coverage run. The status can be Covered, Partially covered, or Not covered. In this example, the status of Covered indicates that this test run exercised all of the map rules.
  • Functional map: Partially covered - This line displays the aggregated coverage status for all map rules that nested functional maps contain. In this example, the status is Partially covered, which indicates that the test runs exercise some functional map rules, but some functional map rules do not execute.
  • Run map: Not covered - This line displays the aggregated coverage status for all run map rules that the RUN function calls. In this example, the status is Not covered, which indicates that no run map rules execute during any of the test runs.