You can select a topic from this diagram:
Use the Code Coverage tool to help test your code.
Code coverage is a way to measure how much code a particular process has executed during a test or benchmark. Using code-coverage analysis, you can then create additional test cases to increase coverage and determine a quantitative measure of code coverage, which is an indirect measure of the quality of your software (or better, a direct measure of the quality of your tests).
Several types of metrics are commonly used in commercial code-coverage tools, ranging from simple line or block coverage (i.e. "this statement was executed") to condition-decision coverage (i.e. "all terms in this Boolean expression are exercised"). A given tool usually provides a combination of types.
The coverage tool in the IDE is a visual front end to the gcov metrics produced by the gcc compiler. These coverage metrics are essentially basic block coverage and branch coverage.
The IDE presents these metrics as line coverage, showing which lines are fully covered, partially covered, and not covered at all. The IDE also presents percentages of coverage in terms of the actual code covered (i.e. not just lines).
Block coverage, sometimes known as line coverage, describes whether a block of code, defined as not having any branch point within (i.e. the path of execution enters from the beginning and exits at the end.) is executed or not.
By tracking the number of times the block of code has been executed, the IDE can determine the total coverage of a particular file or function. The tool also uses this information to show line coverage by analyzing the blocks on each line and determining the level of coverage of each.
Branch coverage can track the path of execution taken between blocks of code. Although this metric is produced by the gcc compiler, currently the IDE doesn't provide this information.
The IDE's code coverage tool works in conjunction with the compiler (gcc), the QNX C library (libc), and optionally the remote target agent (qconn). When code coverage is enabled for an application, the compiler instruments the code so that at run time, each branch execution to a basic block is counted. During the build, the IDE produces data files in order to recreate the program's flow graph and to provide line locations of each block.
 |
Since the IDE creates secondary data files at compilation
time, you must be careful when building your programs in a
multitargeted build environment such as QNX Neutrino.
You must either:
Note also that the compiler's optimizations could produce unexpected results, so you should perform coverage tests on a unoptimized, debug-enabled build. |
When you build a program with the Build with Code Coverage build option enabled and then launch it using a C/C++ QNX Qconn (IP) launch configuration, the instrumented code linked into the process connects to qconn, allowing the coverage data to be read from the process's data space.
But if you launch a coverage-built process with coverage disabled in the launch configuration, this causes the process to write the coverage information to a data file (.da) at run time, rather than read it from the process's data space.
 |
You should use data files only if you're running the local launch configuration on a QNX Neutrino self-hosted development system. Note that the data can later be imported into the IDE code coverage tool. For information about importing gcc coverage data from a project, see Importing gcc code coverage data from a project |
Once a coverage session has begun, you can immediately view the data. The QNX Code Coverage perspective contains a Code Coverage Sessions view that lists previous as well as currently active sessions. You can explore each session and browse the corresponding source files that have received coverage data.
To build executables with code coverage enabled:
|
If the IDE is set to build more than one variant, an error is displayed and the OK button is disabled. |
If you're using your own custom build environment, rather than QNX Makefiles, you'll have to manually pass the coverage option to the compiler.
To enable code coverage for non-QNX projects
-fprofile-arcs -ftest-coverage
If you're using qcc, compile with:
-Wc,-fprofile-arcs -Wc,-ftest-coverage
For example, your Makefile might look something like this:
objects:=Profile.o main.o
CC:=qcc -Vgcc_ntox86
CFLAGS:=-g -Wc,-ftest-coverage -Wc,-fprofile-arcs -I. -I../proflibCPP-std
LDFLAGS:=-p -g -L../proflibCPP-std -lProfLib -lcpp
all: profileCPP-std
clean:
-rm $(objects) profileCPP-std *.bb *.bbg
profileCPP-std: $(objects)
$(CC) $^ -o $@ $(LDFLAGS)
To start a program and measure the code coverage:
If you launched a code coverageenabled build process and chose to disable code coverage in the launch configuration, this causes the process to write the coverage information to a data file (.da) at run time, rather than read it from the process's data space. This means that you can choose to import this data into the IDE Code Coverage tool at a later time.
To import gcc code coverage data from a project:
By default, you will not have the Target File System Navigator tab in your Tasks view. To add this tab to your view:
The project_name.da will be visible under the C/C++ tab for the corresponding project.
Now, the Code Coverage tab displays the session name and imported gcc code coverage data for the selected project.
The QNX Code Coverage perspective includes the following views:
They're described in the pages that follow.