Add XML, SOAP and REST tests in WCS systemtests

[Piero Campalani]

Currently there are only KVP test queries.

We should add equivalent XML, SOAP and REST protocol queries for each of the existing queries.

The oracle should be just one for the three queries, to make it more robust.

Each new WCS test query should be in the three formats as well.

[Piero Campalani]

I'll take this for XML and SOAP.
Alex, afterwards can you add the REST queries?

[Piero Campalani]

XML tests added in changeset:cde6ccf.

Alex, I'm passing on this to you for the .rest queries, no need to tell you why.
(I do not see a critical urgency here for this).

No need for new oracles: now they do not have the protocol extension suffix (e.g. .kvp) since they are unique for the equivalent input queries, independently of their protocol.

[Dimitar Misev]

I will file one more patch under this ticket: marking tests as known to fail. This is done by putting a file known_fails in the test directory, and adding each failing query in one line of the file. The systemtest then automatically considers these queries and marks them in the output as skipped instead of as fail.

[abeccati]

Consider also updating the test system doc page with the known_fails concept

[Dimitar Misev]

Ok, wiki:RasdamanTestSuites#Queriesknowntofail

[Peter Baumann]

note that REST is purely experimental currently, there is not even a complete OGC spec doc.

[Dimitar Misev]

I know we have for REST and XML, not sure about SOAP? Is it planned to add it, or should we close the ticket already?

[Peter Baumann]

SOAP is officially supported so at least a few tests needed (Jin does the rigorous OGC compliance test development so might do this at some time), REST is experimental ( andWCS REST spec is still under discussion, see comment above).

[Piero Campalani]

While REST is experimental, if we provide an endpoint for that then we really should include it in the systemtests.

Regarding SOAP, I suggest not to add any tests query, while defining a template for SOAP requests, and filling the body with the existing .xml tests. Otherwise we land in a hell of tests duplication.

Regarding SOAP again: rigorous compliance is not too rigorous since maybe half of XML POST and SOAP tests are TBD in the WCS 2.0 test suite.

[Peter Baumann]

SOAP: an OGC ETS is supposed to come from the DREAM project this year. In fact, as SOAP uses XML data like POST it should indeed not test the XML payload, but only the SOAP conformance (header/body envelope etc).

for REST there is no complete OGC specification, just a draft. So unclear what to test. The wiki documentation should state clearly that this is a first attempt, used to propose & discuss concepts in OGC, but neither comprehensive nor tested.

[Dimitar Misev]

We have kvp and xml now, and from the discussion it follows that it doesn't make sense to add rest/soap, so closing.