PROIV Code Coverage |
VIRTUAL MACHINE |
 |
|
PROIV Code Coverage |
VIRTUAL MACHINE |
|
Trail: PROIV Documentation > Developer > PROIV Developer > Code Coverage Overview
This section of the manual describes PROIV's support for code coverage.
An issue of concern to developers in all programming languages is how much of their code is being covered by testing. The aim is for testing to have a broad coverage rather than repeatedly exercising a narrow section of the code. An automated tool to provide this code coverage allows developers to have confidence their code is adequately tested. The next section will describe how PROIV can provide this information.
There are three stages to the code coverage process in PROIV:
Additional information for code coverage must be generated while functions are built.
Code coverage data is captured.
Captured code coverage data is reported on.
The code coverage includes which events (with associated logic blocks) for
Cycles
Fields
Files
Functions
Function Keys
have been triggered. The logic blocks (including global logics) are broken down as follows:
which sets of lines (code paths) have been executed;
in some cases which parts of a line have been executed (e.g. inline IF statement);
for IF and CASE statements whether all the paths under their control
have been executed.
This information can be presented as a report or visualized.
See the getting started guide for an introduction.
Topic ID: 700079