Hi Andrea, Does that mean we should be able to get away with only using the pre- existing tests in http://svn.osgeo.org/geotools/branches/2.6.x/modules/library/jdbc/src/test/java/org/geotools/jdbc as well as our created tests in http://svn.osgeo.org/geotools/branches/2.6.x/modules/plugin/jdbc/jdbc-h2/src/test/java/org/geotools/data/ingres? And as such we shouldn't need to do any further testing besides ensuring our code passes those JUnit tests?
Thanks, Anthony On 21-Jan-10, at 1:01 AM, Andrea Aime wrote: > Anthony McCallum ha scritto: >> Hi Andrea, >> I am also working with Lim on this project. This list has already >> proven to be a very valuable resource for us. I have a couple of >> follow-up questions with regard to your reply. One of the areas >> which I will be working on is testing. I understand that we will >> need to create a test class for each class we create. Are these in >> addition to the over 150 test cases which you mentioned? > > The 150 tests are included in a number of abstract test classes that > you have to subclass for your specific database, in order to provide > the database specific setup/teardown sql scripts. > > The abstract test classes and abstract test setups are here: > http://svn.osgeo.org/geotools/branches/2.6.x/modules/library/jdbc/src/test/java/org/geotools/jdbc > and each database has its own specific subclasses, for example see: > http://svn.osgeo.org/geotools/branches/2.6.x/modules/plugin/jdbc/jdbc-h2/src/test/java/org/geotools/data/h2 > http://svn.osgeo.org/geotools/branches/2.6.x/modules/plugin/jdbc/jdbc-postgis/src/test/java/org/geotools/data/postgis > > You'll also have to create property file with the database > connection details. > >> Our initial thought was that we would use an application making use >> of geoserver to ensure that geotools was able to interface >> correctly with ingres. (i.e. a geoserver demo of some sort which >> would perform operations that rely on geotool's ability to read and >> write to external databases (i.e. ingres)) Do you see this as a >> necessary step, or should the JUnit tests be sufficient? > > We usually don't run GeoServer tests against databases as that would > make for a complex setup that few people can replicate (plus, it's > tedious). What we do is to use GeoServer interactively and if a bug > pops up we create a new unit test case in GeoTools to cover it. > > Usually, when your database passes the existing tests you're good to > go with GeoServer as well, minus eventual performance issues (usage > of spatial indexes, efficient translation between the database > native geometry format and JTS geometries and so on). > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
