[CITE-Forum] CSW CITE tests

Richard Martell rmartell at galdosinc.com
Fri Jul 12 18:05:11 EDT 2013

The test case you refer to specifies an illegal acceptversions parameter value; the response entity is expected
to contain:

(a) an ows:ExceptionReport with @version = "1.2.0"  [1]
(b) an exception where @exceptionCode="VersionNegotiationFailed"

[1] No idea why the OGC catalog spec set this version number for exception reports (07-006r1, 10.3.7).

TEAM-Engine v4.0 with the csw-2.0.2-r7 test suite are the current releases.


From: CITE-Forum [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial.org] On Behalf Of Eric Blasenheim
Sent: Friday, 12 July, 2013 06:23
To: cite-forum at lists.opengeospatial.org; CITE SC
Subject: [CITE-Forum] CSW CITE tests

We are seeing some exceptions thrown when we run the Trunk version of the CSW tests locally but we never see these errors when we run the official tests.

My setup for running the tests locally:

•         Source for csw test scripts: https://svn.opengeospatial.org/ogc-projects/cite/scripts/csw/2.0.2/trunk

•         Engine used to run tests: team engine 3.2

A good example of the failures we see locally that passed on the OGC site:


•         Our ExceptionReport has a version number of 1.0.0 whereas the script expects 1.2.0.

•         Our exceptionCode is a custom value “E04002” whereas the script expects “VersionNegotiationFailed”.

So we are wondering why our tests pass but don’t when run locally!  What version is the official tests?

Any ideas?


Eric Blasenheim, Chief Product Architect
Pitney Bowes Software, Group Technology Office
1 Global View, Troy, NY 12180
O: 518-285-7276
eric.blasenheim at pb.com<mailto:eric.blasenheim at pb.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/cite-forum/attachments/20130712/547de55d/attachment.html>

More information about the CITE-Forum mailing list