Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is good to go but wfs 1.1 has some failures (did not investigate the cause).
It's far from complete but at this point a proof of concept that it can work. Among the things to do that come to mind:
* come up with a better way to display the logs
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
** Not sure about this one. That build server is pretty overloaded as it is with all the other build jobs so i am not sure how much running the cite jobs will tax the server. I guess we can see how it goes.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
What a beautiful view. I guess WCS 1.0 is failing because WCS 1.1 was
not disabled?
It seems we're only missing WMS from that party
Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is good to go but wfs 1.1 has some failures (did not investigate the cause).
We've been discussing some of the failures in the "GeoServer 2.0.2 release" thread, basically the xml schema documents returned by DFT
over multiple types contain imports in the middle of the document.
There are other failures too, Victor has been reporting them
It's far from complete but at this point a proof of concept that it can work. Among the things to do that come to mind:
* come up with a better way to display the logs
Yeah, a title and some white space at the end would probably go a long
way to visually separate the list of failures.
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
As a priority I would also add:
- share back the scripts you have in svn
- add the ability (if missing) to copy/paste one failing test and have
the run.sh command run just that
Anyways, props! This looks like a solid step in the right direction
If you need help just ask.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is
good to go but wfs 1.1 has some failures (did not investigate the cause).
It's far from complete but at this point a proof of concept that it can
work. Among the things to do that come to mind:
* come up with a better way to display the logs
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
** Not sure about this one. That build server is pretty overloaded as it
is with all the other build jobs so i am not sure how much running the
cite jobs will tax the server. I guess we can see how it goes.
-Justin
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
What a beautiful view. I guess WCS 1.0 is failing because WCS 1.1 was
not disabled?
It seems we're only missing WMS from that party
Actually I did disable wcs 1.1... not sure where those failures are coming from, need to look a bit deeper.
I am actually having problems with the wms tests running with that version of the tests and engine that is being used. Looking in to that as well.
Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is
good to go but wfs 1.1 has some failures (did not investigate the cause).
We've been discussing some of the failures in the "GeoServer 2.0.2
release" thread, basically the xml schema documents returned by DFT
over multiple types contain imports in the middle of the document.
There are other failures too, Victor has been reporting them
It's far from complete but at this point a proof of concept that it
can work. Among the things to do that come to mind:
* come up with a better way to display the logs
Yeah, a title and some white space at the end would probably go a long
way to visually separate the list of failures.
Should be able to run it through a filter to make it a little nicer. I have a far more evil plan that I hope will work. The plan is to actually do the cite tests run via the command line but also run the server for the purpose of viewing the logs. As long as they run from the same work directories I think it should work... we will find out soon enough.
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
As a priority I would also add:
- share back the scripts you have in svn
- add the ability (if missing) to copy/paste one failing test and have
the run.sh command run just that
+1
Anyways, props! This looks like a solid step in the right direction
If you need help just ask.
Thanks! I am glad it is working better this time around.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is
good to go but wfs 1.1 has some failures (did not investigate the cause).
It's far from complete but at this point a proof of concept that it can
work. Among the things to do that come to mind:
* come up with a better way to display the logs
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
** Not sure about this one. That build server is pretty overloaded as it
is with all the other build jobs so i am not sure how much running the
cite jobs will tax the server. I guess we can see how it goes.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Only wfs 1.0 and wfs 1.1 are set up so far. As you can see wfs 1.0 is
good to go but wfs 1.1 has some failures (did not investigate the cause).
It's far from complete but at this point a proof of concept that it can
work. Among the things to do that come to mind:
* come up with a better way to display the logs
* make scripts for starting and stopping geoserver more robust
* document the setup
* submit the patches back into teamengine
* set up remaining test suites
* move to a separate server **
** Not sure about this one. That build server is pretty overloaded as it
is with all the other build jobs so i am not sure how much running the
cite jobs will tax the server. I guess we can see how it goes.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Sorry a bug in the scripts that was returning success when failures were
present. Should be fixed now. Doing another run to test it.
Thanks a lot, Justin. Looks much better now.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
