I’ve been digging around and found some older posts from last year asking about requirements for a code coverage report. I agree with your assertion that a report should boil down to a simple number for lines covered.
swanlake seemed to have a valuable suggestion for determining which lines are executable in reply to your blog.
- Is there any chance of getting this worked into the 1.8.3 build?
- at a bare minimum (and I would greatly prefer 1 above) could get get the plsql_profiler_runs.runid or plsql_profiler_runs.run_comment within the report so we could provide this report outselves?
Optional 3rd request
Could we get some identifier in PLSQL_PROFILER_RUNS.RUN_COMMENT1 (guid?) that would pull a suite together? Right now it has a different run-id for each test run, it would be nice to be able to tie it all toegher without guessing.