Does TPTP support code coverage? I've spent 20 minutes browsing the docs
and I can't seem to find an answer to the question. If it does would you
point me to some documentation that describes its support and how to use
it?
If not what coverage tools can you recommend? My requirements
1) Supports branch coverage and
2) understands that some lines have several basic blocks (compound if
statements)
3) Integrated with eclipse
4) Free - I'm not ready to justify licensing fees to my management.
TPTP 4.0.1 (what I have played with a bit) only seems to offer method
coverage.
I have used
* djUnit
* coverlipse
for getting coverage from unit tests.
Both are listed at eclipse-plugins.info .
Hi Mark,
Yes, TPTP does support code coverage as a profiling type. However,
TPTP's code coverage is at the method level of granularity. For more
information, see:
Help >> Help Contents >> Monitoring and analyzing application performance >>
Profiling an application >> Using profiling views to analyze data >>
Analyzing method execution >> Viewing code coverage
and
Help >> Contents >> Monitoring and analyzing application performance >>
Profiling an application >> Profiling views >> Using the Code Coverage
Statistics view
Paul
"Mark Levison" <mark.levison@cognos.com> wrote in message
news:cc7d2eb345cb16a51c8943bdc1393ebf$1@www.eclipse.org...
> Does TPTP support code coverage? I've spent 20 minutes browsing the docs
> and I can't seem to find an answer to the question. If it does would you
> point me to some documentation that describes its support and how to use
> it?
>
> If not what coverage tools can you recommend? My requirements
> 1) Supports branch coverage and
> 2) understands that some lines have several basic blocks (compound if
> statements)
> 3) Integrated with eclipse
> 4) Free - I'm not ready to justify licensing fees to my management.
>
Thanks for the replies in the end I tried
1) Coverlipse
2) djUnit
3) Emma
and for now I've choosen Emma for its speed (even though the eclipse
integration is still very new. Its only serious failing so far its funny
handling of exceptions. If an exception is thrown part way through a
block, it doesn't consider that block covered. This is a bit of hassle
with our unit tests where we check all of our exceptional conditions.