Thread Subject: Getting code coverage information programmatically

Hi,

I wondered if it's possible to get code coverage
statistics programmatically using the profiler.

For example, if I run the code
profile on;
msgbox('Some string');
profile viewer;

Then the viewer tells me how many lines of code are in the
msgbox function (209) and how many of these my function
call has hit (91). I'd like to get this information in
code rather than through the viewer, but I only seem to be
able to get information about which lines of code have
been executed and nothing about the remaining lines.
(Using the profile('info') call and then looking in the
FunctionTable.ExecutedLines bit of the structure).

Does anybody know if what I'm trying to do is currently
possible?

Thanks,

Rich N

"Richard Nicholson" wrote:
> I wondered if it's possible to get code coverage
> statistics programmatically using the profiler.

Hi Richard:

Getting the correct coverage statistics can be quite
complicated if you use subfunctions, nested functions, and
anonymous functions, but for simple situations, you can do
this (in R2007a).

>> profile on
>> imagesc(magic(5)) % Your code here...
>> profile off
>> runnableLineIndex = callstats('file_lines','magic')

runnableLineIndex =
 13 16 17 18 19 20 23 24 25 26 27 30 31 32 33 34 35
 36 37 38 39 40 41 42

These are the line numbers that can potentially be run for
each function ("magic" in this case). As you indicated, the
profiler info structure tells you which ones actually DID run.

This particular hook into callstats is undocumented and may
change in the future, so use at your own risk.

-Ned.