On Tue, May 10, 2011 at 3:22 AM, Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> wrote: > +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.
A db implementing all tests should have around 250 of them. Some db like postgis having the choice between prepared and non prepared statements have around 500 total (each test run with both configurations, prepared and not). If we could stick the jdbc code inside the h2 or postgis modules I bet we'd get between 80 and 90% coverage. Too bad the existing tools does not allow to realize this... Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ 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
