Justin, the community module process requires an overall module unit test coverage of 40% for promotion: http://docs.geoserver.org/1.7.x/developer/policies/community-modules.html
I can generate lovely and revealing reports with mvn cobertura:clean cobertura:cobertura but I do not see any overall module summary for either line or branch coverage. How do you recommend assessing a module against the 40% coverage requirement? One weakness I notice in the coverage reports is that simple classes that implement giant APIs (e.g. Collection, FeatureCollection) come off poorly because they have many methods that consist entirely of "throw new UnsupportedOperationException();". Is there any way to exclude these from statistics, or are they there to remind us that giant APIs are a code smell? Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
