#64 Conditional Statistics and Warnings possible?

[Kurt]

I LOVE EMMA and have shared it with my whole project
team! Thank you for the great work!

Before I found EMMA, I was evaluating some high priced
commercial products. One of which was Clover. (I liked
it because it was integrated very nicely into Eclipse.
But that's an entirely different Feature Request!)
Anyway, one thing it did differently than (or in addition
to) EMMA was it gave me something that I'm going to
call "Conditional Statistics and Warnings". Although that
is probably not the proper terminology.

After Clover executed my JUnit test suites, it gave me a
warning indicator next to one of my if() statements in
my code under test. When I "moused over" the warning
indicator, it told me in a pop-up that this particular
conditional statement had evaluated to true 15 times
and had evaluated to false 0 times.

This has nothing to do with code coverage in the strict
sense. It's more deep than simple code coverage.
Since it had evaluated to true so often, the code inside
the if() block had executed and was fully covered. But
because it had never actually evaluated to false, there
was a condition in my code that my JUnit test had never
actually tested, even though the code was fully covered.

Is this a functionality that could be added to EMMA
without too much effort? If it is a performance issue,
then please consider having it turned OFF by default.

Thanks for listening,
Kurt from Florida