Thank you both for your reply, Let me take those two emails as "expressing interest" so we should not cancel this activity. I will update the blog post to indicate "email geoserver-devel" if interested and we can extend the deadline until the end of next week. I would like to evaluate and select a proposal during our next geoserver meeting.
To answer Gabriel's question there are three main approaches that have been discussed so far: a) cite command line: The existing scripts made use of a the cite engine to run tests on the command line. It was tricky to run a GeoServer, wait for it to startup, and then perform the tests. These jobs are still on build.geoserver.org and can be used a a reference. b) cite engine service: The new cite engine has a rest-api, so the testing script could use CURL commands to ask the engine to run the tests c) cite engine docker: The cite engine is also distributed as a docker image, if that makes it easier to manage the rest-api approach Any of those approaches can be viable, the challenge (after our last experience) is setting up something that can be maintained. Other notes: - The WFS-T tests required a database to run, the tests created a couple of tables each time (since the transaction request modifies the content) -- Jody -- Jody Garnett
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
