On 4/30/2014 11:39 AM, Colson, Edmund B wrote:
May I assume that there is some documentation on how this function works within RDi 9.1? Some examples or verbiage to help with creating and setting up the function? Does anyone know this yet?
Here's the announcement letter:
Line level code coverage analysis capability. Code coverage can be
launched on any program or service program that can be debugged. The
developer can then see by views, html reports, and editor annotations
exactly which lines of the programs have been execute or not executed by
that particular scenario. This can provide a great benefit in measuring
the effectiveness of automated or manual tests. It can help focus
additional testing on code paths that have not been executed. It can aid
the reduction of the amount of testing required by eliminating tests
that are duplicate in terms of which code paths they exercise.
The documentation isn't out yet, but the idea is pretty simple. Use the
debug API QteStep to have RDi step through a program under debug and
record all the line numbers that were touched. From that, you can
create a list of lines touched (and how many times) as well as a list of
lines UNtouched.
I'd imagine a right click on the source member, similar to setting a SEP
debug session. But instead of debug, it does debug and step into,
prompting you to run the program. As the program runs, line coverage
collects the stats and when the program ends, RDi presents the report.
If you're interested in the debugger APIs, this has some simple samples:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/apiref/apiexusdeb.htm
--buck
midrange.com
