The diagram above illustrates the various pathvIEw components and the processes involved.
(1) Standard CA Gen source code is generated (from the toolset or encyclopaedia). Prior to compilation, it is modified by the pathvIEw Source Code Post-Processor, which adds in calls to the pathvIEw runtime to log statement executions.
(2) The modified source code is then installed and made available for execution in the testing region.
(3) On execution of the application, statement coverage data is gathered by the pathvIEw runtime, and sent (using TCP/IP) to the pathvIEw Listener at the end of the transaction. The Listener stores the execution results in the pathvIEw database. The Listener is a multi-threaded application that supports the logging from multiple application executables in parallel.
(4) The code coverage data can be viewed at any time using the pathvIEw client. Summary information provides a quick overview of the degree of testing. Filters are available to select which action blocks are displayed, for example by Change Request or Test Case.
Detailing the action block opens the Statement Coverage window.
This shows the statements that have been executed in green and those not executed in red with a useful overview of the entire action diagram on the left hand side.