+1. Some things are hard to test (GUI, network [e.g. JDBC]), so rather than an absolute rule for for all modules, those falling below 40% for offline tests may have to refer to online tests or special pleading. Some modules have low coverage in their own tests but are massively covered by tests in other modules.
Having a look in modules/library: main: 49% xml: 47% referencing: 48% jdbc: 8% JDBC is an obvious case where the offline tests are minimal, but online tests in the implementation modules is rather good, IIRC. On 09/05/11 18:18, Jody Garnett wrote: > Given that Andrea is the source of all truth (or was it the Pope? someone in > italy). > Could we make a motion to update the developers guide with a consistent > target of 40%? -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
