We talked about this before, having a single config or having separate.
We agreed on separate because I believe that some of the tests get
thrown off when when you have more types then they expect around.
However I believe this only occurs for wfs 1.0 and wfs 1.1, so while not
100% sure I think we would need a seperate configuration for wfs 1.1,
which led us to go with the separate configuration directories.
I also find it easier to debug tests with less feature types around.
As for the UTF-8 issue... I am unsure how to solve this. Arne: you had
the idea of using a zip file, I think this would get around the svn
checkout issue... but what about when the archive is unpacked... I think
the same problem with storing file names with extended latin characters
would still occur.
As for citewcs... I do believe its incomplete (on trunk), we need to
move over the files from the cite configuration on 1.5.x. Also, i
suggest we rename it to citewcs-1.0 with wcs 1.1 coming down the pipe.
Other peoples thoughts?
-Justin
Arne Kepp wrote:
Hi,
when I was running the CITE tests last week I ran into some unexpected
problems. I found the documentation Justin had written
(http://docs.codehaus.org/display/GEOSDOC/1+Running+CITE+Tests) very
helpful, and I added a few hints regarding text encoding and WFS 1.1
tests, but got stuck in several places.
In particular, it is not clear what dataset should be used for a given
test. WCS is particularly confusing, because the configuration directory
is incomplete (
http://svn.codehaus.org/geoserver/trunk/configuration/citewcs/ ). Andrea
said he was able to complete the WCS tests using the "cite" directory,
but I was not able to replicate this. Ideally, I think we would want a
permanent installation somewhere that would only require and svn update
to run the tests again. I tried setting this up on Artois, but limited
UTF-8 support on that machine prevents me from creating a useful
environment for WFS-1.1.
Does anyone have any clear idea of how we can improve upon this? Is
there anything preventing us from running all the tests from a single
configuration? Can any / all of the other configurations in Subversion
be deleted, to avoid confusion?
-Arne
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,472609eb74221804284693!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org