Converts coverage data to an XML format. By default, the XML is written to the standard output.
The XML format is described below.
<?xml version="1.0" encoding="UTF-8"?> <BullseyeCoverage name="basename" dir="directory" buildId="buildId" version="6" xmlns="https://www.bullseye.com/covxml" summary-measurements> <!-- sequence of <folder> and <src> elements --> </BullseyeCoverage>
|The basename of the coverage file|
|The source directory. The source and folder names are relative to this directory|
|Identifies the last change made to the coverage file as a result of building|
<folder name="basename" summary-measurements> <!-- sequence of <folder> and <src> elements --> </folder>
|basename of folder|
<src name="basename" mtime="n" summary-measurements> <!-- sequence of <fn> elements --> </src>
|basename of source file|
|timestamp of source file in seconds since the Epoch|
<fn name="function-name" summary-measurements> <!-- sequence of <probe> elements --> <!-- sequence of <block> elements --> </fn>
<probe line="n" column="n" col_seq="n" kind="kind" event="event"/>
|Source file line number|
|Beginning column number of the code measured by the probe, not counting whitespace. If not present, the value is zero.|
|Column sequence number. Uniquely identifies probes having the same line and column. If not present, the value is zero.|
|One of: |
<block line="n" entered="entered"/>
|Source file line number|
If the block was entered,
the value |
block element is provided to assist with importation to a system that accepts statement coverage or basic block coverage,
but cannot use the condition/decision coverage provided by the
You can ignore this element unless you have such a restriction.
This information is similar to statement coverage
but does not meet the requirement of statement coverage for safety-critical certification.
block element indicates whether a block of contiguous statements was reached.
The statements are either a function body,
or substatements in a control structure reached by a conditional branch.
A statement reached does not imply the statement completed or that subsequent statements were reached.
block elements are derived from condition/decision coverage as described in Instrumentation Model.
Some information available in the
probe elements has no representation in the
For example, the events listed below are not indicated.
||operators and the
defaultwithin a sequence of
fn_cov="n" fn_total="n" cd_cov="n" cd_total="n" d_cov="n" d_total="n"
|number of functions invoked for the region|
|total number of functions in the region|
|number of conditions and decisions invoked for the region|
|total number of conditions and decisions in the region|
|number of decisions invoked for the region|
|total number of decisions in the region|
We recommend ignoring the decision coverage measurements,
Decision coverage may report uncovered code as covered.
Use these measurements only to compare with results from other tools that cannot provide condition/decision coverage.
|The coverage file is specified by Path. The default is |
|Display a summary of options.|
|Write XML to Output instead of standard output|
|Suppress warnings and the copyright message.|
|Suppress startup banner|
Include a style sheet reference.
When used with |
|The coverage file. Option |
|Configuration file. See FILES.|
If the files listed below exist, they contain initial options separated by white space.
Within such files,
$NAME is replaced by the value of environment variable NAME.
|File Version||Software Version||Date||Changes|
Remove root element attribute |
Add root tag attribute |
|6||8.20.0||Oct 2020||Add |
Last update: 26 Jan 2022
Copyright © Bullseye Testing Technology. All Rights Reserved.