PostGIS tests need to be rewritten
----------------------------------

         Key: GEOT-702
         URL: http://jira.codehaus.org/browse/GEOT-702
     Project: GeoTools
        Type: Bug
  Components: postgis  
    Versions: 2.2.M1, 2.1.1    
 Reporter: Cory Horner
 Assigned to: Chris Holmes 
    Priority: Blocker


With the demise of feathers.leeds.ac.uk (the former postgis_test database), 
we've lost the ability to perform tests on the PostGIS plugin (most tests are 
disabled).  Refractions will be hosting the replacement PostGIS implementation, 
but without the original data from feathers, the tests will need to rewritten 
and/or database populated.

Jody wrote:

"We lost the geotools test server (called feathers) some months ago, so
PostGIS QA tests have not been run for a while. I have started setting
up some new read only tests, and we have connection information for a
scratch database we can use for read/write tests.

We have backed out the changes that caused the Feature Type problems, it
sounds like there is also a BBox problem for WMS that I have not heard
more details about.

So what I really should do is ask for help ... the database connection
information is here:
-<http://svn.geotools.org/geotools/branches/aggregates/plugin/postgis/test/org/geotools/data/postgis/demo-bc-fixture.properties>
-<http://svn.geotools.org/geotools/branches/aggregates/plugin/postgis/test/org/geotools/data/postgis/geotools-test-fixture.properties>
-<http://svn.geotools.org/geotools/branches/aggregates/plugin/postgis/test/org/geotools/data/postgis/fixture.properties>

Ideas:
1. We can port the PostGisDataStoreAPI test over to fixture.properties
(so it will only run against a local postgis install?)
2. PostgisDataStoreTest against geotools-test.fixture
3. Create some kind of PostgisDataStoreReadonly test against
demo-bc-fixture.properties

Once again if anyone can find the contents that used to be on feathers
it will save us rewriting PostgisDataStoreTest.
> We already have problems reading a large layer (always in post gis)
> because some features doesn´t appears  reading from Geoserver (simple
> getmap request), but those features appears when reading using another
> software (UDIG reading directly from postgis) this problem was using
> RC2 release.
UDIG has its own subclass of the PostGIS DataStore, it was my attempt to
merge the optimizations back to geotools that created these problems (should 
not of even tried without test cases)."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to