About Code Coverage

Source-code coverage consists of identifying which portions of a program are executed or not during a given test case. Source-code coverage is recognized as one of the most effective ways of assessing the efficiency of the test cases applied to a software application.

The Code Coverage feature brings efficient, easy-to-use robust coverage technologies to real-time embedded systems. Code Coverage provides a completely automated and proven solution for C, C++, Ada and software coverage based on optimized source-code instrumentation.

Code Coverage supports the following languages:

How Code Coverage Works

When an application node is executed, the source code is instrumented by the Instrumentor (attolcc4, attolcpp, attolcc1, attolada). The resulting source code is then executed and the Code Coverage feature outputs an .fdc and a dynamic .tio file.

These files can be viewed and controlled from the OneTest Embedded GUI. Both the .fdc and .tio files need to be opened simultaneously to view the report.

Of course, these steps are mostly transparent to the user when the test or application node is executed in the OneTest Embedded GUI or Eclipse (for C and C++).

 

To learn about

See

Obtaining a Code Coverage report for your application source code

Using Runtime Analysis Features

Coverage types

Selecting Coverage Types

SCI technology as used by Code Coverage

Source Code Insertion Technology

Using the Code Coverage Viewer

About the Code Coverage Viewer

 

Related Topics

Runtime AnalysisAbout Static MetricsSource code insertion overview