Ok, i have packed up the cite tools and updated the cite README. This packed
up version contains all the hacks that I had to put in place to get the
tests to run. Feel free to examine the svn diffs.

  http://files.opengeo.org/cite_tools.tgz

Once someone else (Andrea or Gabriel) tries this out and verifies it
actually works I will update the online release guide documentation.

I will also probably create a github repo or something to store all of this
so that (a) if the build server goes bye bye we won't lose the patches and
(b) we can still leave it linked to ogc svn.

-Justin

On Wed, Jan 5, 2011 at 10:48 AM, Justin Deoliveira <jdeol...@opengeo.org>wrote:

> Sadly those instructions are out of date. Sigh... the cite testing story
> right now is quite a mess.
>
> What I will do is zip up the cite testing tools that i have on the build
> server and make those available for download, encouraging devs to just run
> the tests from that. With all the patches I have had to make it has become
> tricky to manage.
>
> More shortly.
>
> -Justin
>
> On Wed, Jan 5, 2011 at 10:42 AM, Gabriel Roldán <grol...@opengeo.org>wrote:
>
>> On Wed, 2011-01-05 at 10:29 -0700, Justin Deoliveira wrote:
>> > Hmmm... what version of the tests are you running?
>> >
>> just followed the README in community/cite to the letter and ran the
>> test suite through run.sh wms-1.1.1.
>> The VendorSpecificCapabilities failure hudson is reported should be
>> fixed now, but it keeps complaining when I do a manual run in hudson.
>> How does the cite-wms-1.1.1 hudson build is run? does it depend of a
>> geoserver trunk build, nightly, or deploy?
>> >
>> > I just looked at the sources of those tests and it looks like the
>> > WMTVER rather than VERSION parameter should be used. But it does not
>> > look like it with the url you posted in. Are you positive that is the
>> > url being requested?
>> Didn't debug it, but that's the URL the test log says it's issuing?
>> Could this be to a badly applied patch (one of the ones in the README)?
>> cause I couldn't run the suite through jetty.
>> >
>> > On Wed, Jan 5, 2011 at 9:42 AM, Gabriel Roldán <grol...@opengeo.org>
>> > wrote:
>> >         I fixed the cite failure I recognized as my fault (empty
>> >         VendorSpecificCapabilities), but now when I run it locally it
>> >         the
>> >         following assertion fails:
>> >
>> >         <quote>
>> >         Test wms:wmsops-getcapabilities-params-request-1
>> >         (wms-1.1.1/d40e1042_1)
>> >
>> >         Assertion: When REQUEST is &quot;capabilities&quot;, then the
>> >         response
>> >         is capabilities XML.
>> >
>> >         Request d40e3116_1:
>> >           Method: get
>> >           URL:
>> >
>> http://localhost:9090/geoserver/wms?SERVICE=WMS&&SeRvIcE=WMS&ReQuEsT=capabilities
>> >           Response from parser ::
>> >              <WMS_Capabilities xmlns="http://www.opengis.net/wms";
>> >         </quote>
>> >
>> >         Now, the capabilities URL I gave to the test engine has the
>> >         version=1.1.1 parameter, not sure why the engine is trying the
>> >         above
>> >         request without version parameter, and hence the failure is
>> >         due to the
>> >         WMS 1.3 getcaps being returned instead of the 1.1.1 ones.
>> >
>> >         Any clue?
>> >
>> >         Cheers,
>> >         Gabriel
>> >
>> >         On Wed, 2011-01-05 at 06:47 +0000, Hudson wrote:
>> >         > See
>> >         <http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/136/>
>> >         >
>> >         > ------------------------------------------
>> >         > [...truncated 1147 lines...]
>> >         ...
>> >         >    Test wms:main Failed (Inherited failure)
>> >         > Suite wms:main_wms Failed
>> >         >
>> >         <
>> http://hudson.opengeo.org/hudson/job/cite-wms-1.1-trunk/ws/tools>
>> >         > cp target/sessions/session.xml.wms-1.1.1
>> >         users/geoserver/wms-1.1.1/session.xml
>> >         > Test wms:main (wms-1.1.1) Failed (Inherited Failure)
>> >         >    Test wms:wmsops-getcapabilities-response-2
>> >         (wms-1.1.1/d39e1639_1) Failed
>> >         > RETURN=1
>> >         > Pinging GeoServer at http://localhost:11010/geoserver
>> >         >
>> >         > curl: (7) couldn't connect to host
>> >         > GeoServer is offline
>> >         >
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> >         Learn how Oracle Real Application Clusters (RAC) One Node
>> >         allows customers
>> >         to consolidate database storage, standardize their database
>> >         environment, and,
>> >         should the need arise, upgrade to a full multi-node Oracle RAC
>> >         database
>> >         without downtime or disruption
>> >         http://p.sf.net/sfu/oracle-sfdevnl
>> >         _______________________________________________
>> >         Geoserver-devel mailing list
>> >         Geoserver-devel@lists.sourceforge.net
>> >         https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> >
>> >
>> >
>> > --
>> > Justin Deoliveira
>> > OpenGeo - http://opengeo.org
>> > Enterprise support for open source geospatial.
>> >
>> >
>>
>> --
>> Gabriel Roldan
>> grol...@opengeo.org
>> Expert service straight from the developers
>>
>>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to