All Time and again I am hearing comments on the quality of test coverage for jWebUnit. So I spent this weekend trying to integrate with a code coverage tool called GroboUtils. The good news is that our coverage is reasonable (80%). But there are a couple of important things to do
  1. Improve coverage by writing more test cases (We need to get to the 90%+ range)
  2. Make Grobo toolkit an integral part of the build
I think I can do item #2 easily. (I have already done it!) would it make sense for me to commit these changes? Please let me know. Rgds Vivek


  • FunctionLineCountTOTAL
    functions CoveredTotal functions% Coveredlines CoveredTotal lines% CoveredUnits CoveredTotal Units% Covered
    All Packages28234980.8063879180.669201,14080.70
    PackageFunctionLineCountTOTAL
    functions CoveredTotal functions% Coveredlines CoveredTotal lines% CoveredUnits CoveredTotal Units% Covered
    net.sourceforge.jwebunit.util1128.3332711.1143910.26
    net.sourceforge.jwebunit27533183.0859672182.668711,05282.79
    net.sourceforge.jwebunit.util.reflect66100.00394390.70454991.84


    Do you Yahoo!?
    Friends. Fun. Try the all-new Yahoo! Messenger
  • Reply via email to