Originally posted by Pradip Bhat: I am evaluating code coverage tool. can someone help me in listing the features that I should be looking at.
1. Good Reporting like listing uncovered lines etc 2. Integration with Eclipse,JUnit
We use Emma code coverage tool in our organization. Though this open source tool covers most of our requirements,
I suggest you check for some of the following features in your evaluation tool :
1. If Ant task is supported, ensure that there is a task which would break the build if the statictics are below the expected value.
2. Better summary page: We run this tool to know and identify the classes with less coverage. If you run into 1000 of files spread across multiple packages, it's a pain to go through each and every package and check for the coverage data. If your tool provides a summary page which list all the classes which are falling below expected value, it makes things much easier...