[CITE-Forum] Failed WMS Tests

Richard Martell rmartell at galdosinc.com
Thu Nov 6 17:22:09 EST 2014

Hi Bruce,

You may have noted that the failing tests showed an empty response/content element. 
For some reason a NullParser was configured for these tests; but it looks like this has been fixed for the next release (8).

-- Richard

-----Original Message-----
From: CITE-Forum [mailto:cite-forum-bounces at lists.opengeospatial.org] On Behalf Of Bruce Dietrich
Sent: Tuesday, 04 November, 2014 04:58
To: cite-forum at lists.opengeospatial.org
Subject: [CITE-Forum] Failed WMS Tests

I am working on OGC WMS 1.1.1 compliance testing at http://cite.opengeospatial.org/teamengine/ version r7.  Currently there are two tests failing, both in the same manner.  The tests verify that proper OGC exceptions are returned "LayerNotDefined" when and invalid layer name is requested "NonExistant".  There are three such tests listed below:

#1) GetMapParams Layers-5 s0004/d1e1711_1   LaYeRs=NonExistant
#2) GetMapParams Layers-6 s0004/d1e1723_1   LaYeRs=cite:Lakes,NonExistant
#3) GetMapParams Layers-7 s0004/d1e1737_1   LaYeRs=NonExistant,cite:Lakes

All three are similar GetMap requests but contain an invalid Layers= parameter that should cause the OGC service exception LayerNotDefined.  The Layers parameter is shown for each test above.  Debug code within our WMS indicate that all three of these requests return the same service exception "LayerNotDefined".  The OGC Team Engine results indicate that test #3 above succeeds with the proper service exception shown below:

Request d1e9419_1:
   Method: get
   Response from parser ::
      <ServiceExceptionReport version="1.1.1">
   <ServiceException code="LayerNotDefined"><error>Invalid parameter LAYER.</error><description>The layer nonexistant is not defined.</description></ServiceException>
   <!--Response received in [125] milliseconds--></ServiceExceptionReport>

Result: Passed

However, both tests #1 and #2 above fail with the following output in the OGC Team Engine results.  In both cases, debug code in the WMS indicate the same service exception was returned as in #3.

Request d1e9328_1:
   Method: get
   Response from parser parsers:HTTPParser:
   <status code="200" protocol="HTTP/1.1">OK</status>
      <header name="Server">HiPER LOOK Web Server</header>
      <header name="Date">Tue, 04 Nov 2014 12:29:02 GMT</header>
      <header name="Content-Type">application/vnd.ogc.se_xml</header>
      <header name="Content-Length">399</header>
   <!--Response received in [76] milliseconds--></response>

Result: Failed

Has this been seen before? Is this a problem with the test script or is there something in our response that could trigger this?


Bruce Dietrich
Pixia Corporation
CITE-Forum mailing list
CITE-Forum at lists.opengeospatial.org

More information about the CITE-Forum mailing list