Code Coverage and Profiling |
VIRTUAL MACHINE |
 |
|
Code Coverage and Profiling |
VIRTUAL MACHINE |
|
Trail: PROIV Documentation > Developer > PROIV Developer > Code Coverage > Profiling and Code Coverage
PROIV supports the profiling of functions (i.e. screens, updates, reports etc). This can be used to show detailed breakdown of the function's execution time. It has similarities with but is not the same as code coverage.
Profiling and code coverage use an (internal) instrumentation layer inside PROIV to monitor the execution of functions. It is not possible to have code coverage and profiling enabled at the same time since they cannot share this instrumentation layer. Also the execution overheads of code coverage would skew the profiling results; invalidating them.
If the profiler is enabled in the configuration then programmatically enabling the code coverage will fail with an error. The PROIV Dashboard will not allow profiling and code coverage (capture) to be enabled at the same time. The generation of additional code coverage information at function build can be enabled while profiling.
The essential rule is that profiling always takes priority over code coverage (capture).
Topic ID: 700085