Once risky code is identified, appropriate measures can be taken to heavily test it or even to re-engineer it. HindSight instruments your source code and creates an executable that, as you run your program, stores test coverage information in databases. Function coverage is the number of functions that have been called. One hundred percent function coverage should be achieved before a product is released. If a function isn't tested, there may be a requirement that isn't being tested.
Conditional coverage is the number of true and false conditions that have been tested.
One hundred percent conditional coverage should be achieved at the unit testing level. If a condition isn't tested, an untested piece of code might be executed by the customer causing unexpected results. The appropriate level of test coverage to use depends on the goals of the testing. This is why HindSight provides a variety of test coverage levels. But data is only data unless it can be analyzed in a useful way.