A sample report generated by the tool :
Detailed report on the lines covered by the unit tests written for the project:
Feature List :
[This feature list is quoted from official cobertura page : http://cobertura.sourceforge.net/index.html ]
[This feature list is quoted from official cobertura page : http://cobertura.sourceforge.net/index.html ]
- Can be executed from ant or from the command line.
- Instruments Java bytecode after it has been compiled.
- Can generate reports in HTML or XML.
- Shows the percentage of lines and branches covered for each class, each package, and for the overall project.
- Shows the McCabe cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package, and for the overall product.
- Can sort HTML results by class name, percent of lines covered, percent of branches covered, etc. And can sort in ascending or decending order.
I am sure Java lovers will find it great and indeed a nice tool through which you can justify that your code is stable and it RoCks. :) Enjoy !.
4 comments:
Just remember to back your code coverage report with exhaustive Test cases. Code coverage by themselves cannot be the sole indicator of stable and working code :).
This seem to be a pretty interesting tool. It's really good to have some real numerical data on how much code has been covered rather than pretty much hunching up to your boss with some stupid percentages :P.
But then again, mere code coverage doesn't warrant the non-existence of logical errors, as shams pointed out. So everything seems right to me except for the title :).
It's really nice that you brought up few of the possible good points of this open source project here in your blog which is really impressive!
Nothing offensive but being curious i would like to ask - In which context are you defining the word "Code is Stable!"? How and When we could call that my Code is Stable?
Is there any way i could expect a new post on that? :)
Great work.
Post a Comment