Note: This facility is supported in native COBOL only.
The following restrictions apply to test coverage:
- Test coverage does not support nested programs. In particular, it does not work for programs which call the
cobsetjmp() and
coblongjmp() APIs that are used when calling nested programs.
- Manually changing the execution point while debugging a program produces test coverage results that are unpredictable.
- If you have a multi-threaded program (one that is compiled with the REENTRANT directive) and you compile it with the test
coverage enabled and run it under test coverage, the test coverage results obtained will be unpredictable.
- When you use test coverage with preprocessors, only the basic blocks of the original code are taken into account.
Micro Focus recommends that you do not use test coverage in a production system because of the increased requirements on system
resources when running in test coverage mode. However, you can compile with test coverage enabled into your production system,
if needed.
Additionally, you should exercise caution when enabling code coverage on large remote projects, as this results in a significant
amount of data transfer caused by the required project files being transferred locally for processing of the test coverage
results.