Bug fixes, GetFeatureInfo tests, RESTful tests

[cmorriscmps]

Contains bug fixes as well as options to execute tests for the GetFeatureInfo operation and the REST encoding.

Summary of Changes:

wmtsFunctions.xml

• Fixed many broken tests by globally replacing "$wmts.capabilities.doc/" with "$wmts.capabilities.doc//" in wmtsFunctions.xml.
• Fixed layer selection XPaths to make sure that the layer tested does not contain a dimension without a default.
• Changed the GetTile.Valid.Tile.Transparency test so that setting up a transparent layer is not required. Even if no layer contains the keyword "transparent" in its metadata, the test will still check a layer for transparency and simply return a warning if no transparent pixels are found.
• Removed redundant tests GetCapabilities.Response.Layer.LegendURL.Correct.Format and GetCapabilities.Response.Layer.LegendURL.Correct.Size since they are fully covered by GetCapabilities.Response.Layer.LegendURL.Correct.Resource.
• Fixed legend URL checks to not require height, width, minScaleDenominator, and maxScaleDenominator attributes on legend URLs.
• Fixed bugs in GetFeatureInfo and REST tests.

WMTS_ETS.xml

• Moved starting form from the wmts:main test to the suite element to simplify adding options.
• Added option to fail early on validation errors.
• Added options to enable GetFeatureInfo and REST tests.

owsFunctions.xml

• Fixed bugs in owsFunctions:validateExceptionReport function.

bootstrap.xml

• Fixed test prerequisites as necessary

[dstenger]

This pull request will be on hold until https://github.com/opengeospatial/teamengine/pull/593 is merged and installed on Beta.

[cmorriscmps]

The reference implementation @dstenger provided was failing due to an issue with style selection in the Server.KVP.GET.GetTile.Valid.Tile.Transparency test. I've fixed it and the RI now passes.

[cmorriscmps]

I really have no idea what the purpose of wmts-auto.xml was supposed to be. It appeared to be a copy of WMTS_ETS.xml, except wmts-auto.xml includes other files with xinclude. It doesn't really make sense to maintain two copies of the file. The config.xml file references the ctl directory, which loads all of the ctl files. They are all loaded twice if wmts-auto.xml is included.

[dstenger]

The wmts-auto.xml file is used by the CtlController which is executed by the already mentioned REST interface and command line interface. In addition to the includes, graphics content (java.awt) is removed.

I just checked the file and it seems that all changes are required by the REST interface.

So, I propose to restore the file to make this pull requests merge able.

However, I agree that the implementation should reduce duplication. So, we could create a new issue with the aim to improve/simplify/merge the two main CTL scripts.

[dstenger]

@cmorriscmps I will restore wmts-auto.xmlwhen I merge the pull requests to make it workable with the REST interface again.

Also, I am currently doing a functional review of the pull request and come back to you if I have any questions.

[dstenger]

I did a functional review of the pull request and these are my results.

Questions:

• What is the use case of the new option Fail early on schema validation errors? Can it be used to speed up test runs?

This should be adjusted:

• Upload button for WMTS capabilities document is missing in Web Browser Interface and should be added again.
• Abstract Test Suite (ATS) should also be adjusted (https://github.com/opengeospatial/ets-wmts10/blob/master/src/site/resources/ats.html). E.g. replaced tests should be removed.
• As WMTS_ETS.xml was improved, wmts-auto.xml must be added and adjusted accordingly. wmts-auto.xml is used by REST interface.
  • It should be made sure that following tests are executed by the REST interface: The added mandatory tests of GetCapabilities.main and GetTile.main conformance classes.
  • Unofficial tests for GetFeatureInfo and RESTful Encoding shall not be executed.
  • Optionally, the user can control via a parameter which conformance classes are executed.

Further comments:

• Re-enabling and fixing tests is useful.
• All added tests in GetCapabilities.main and GetTile.main conformance classes are marked as mandatory by ATS. Thus, adding them improves the test suite. Background: This pull request originally disabled them: https://github.com/opengeospatial/ets-wmts10/pull/28.
• The reference implementation passes all added tests (or skips them).
• Test Server.KVP.GET.GetCapabilities.Request.Sections.Contents (enabled by this pull request) is not listed in ATS. However, the test was not modified by this pull request. Thus, this is a separate issue.
• Re-enabling unofficial tests for GetFeatureInfo and RESTful Encoding in Web Browser Interface might be useful. However, those cannot be used for certification. Thus, an additional hint might be added. To be discussed with @ghobona.

[dstenger]

@cmorriscmps Thank you for the good pull request again. However, there are some things which need to be adjusted. Can you please check the list under This should be adjusted: in comment https://github.com/opengeospatial/ets-wmts10/pull/78#issuecomment-1894208642. Also, the options to enable GetFeatureInfo and REST tests shall be renamed to Include GetFeatureInfo Tests (optional) and Include RESTful Encoding Tests (optional) in the UI. If it is not possible for you to work on the changes, please contact me as I can support you here.

[cmorriscmps]

I'll take a closer look and respond by the end of the week.

[cmorriscmps]

To answer the question about the "Fail early on schema validation errors" option, If the option is selected then the root test will validate the capabilities document against the schema and fail without executing any subtests if validation fails. So yes, it will speed up test runs if validation fails.

I agree that the upload button for a capabilities document and that the wmts-auto.xml file should be restored. I can update the pull request with these changes.

I also agree that the ATS needs to be updated to reflect the current state of the ETS. However, it has been out of date long before this pull request was introduced, so I don't think that updating it falls under the scope of this pull request.

[dstenger]

Thank you for updating the pull request. Most problems are solved, now. There are some small tasks which are still pending:

• Rename of optional tests in UI (see https://github.com/opengeospatial/ets-wmts10/pull/78#issuecomment-1904216046)
• Upload button is still missing (see https://github.com/opengeospatial/ets-wmts10/pull/78#issuecomment-1894208642)
• I agree that the ATS must be updated in general. However, I am in favor of removing at least the deleted tests as this should be straight forward.
• Following properties in pom.xml must be updated as the integration-tests fail otherwise (can be activated with Maven profile -Pintegration-tests; they require Docker):

  <soapui.tests.passed>39</soapui.tests.passed>
  <soapui.tests.skipped>20</soapui.tests.skipped>

@cmorriscmps Are you still working on updating the pull request? Can you please give me a short update if you need any assistance?

[cmorriscmps]

@dstenger I'm done with the pull request.

I've fixed the optional test labels.

The Upload capability has been restored. There is no Upload button on the initial form, but if you leave the Capabilities URL field blank, it will present another form asking for a file upload.

Feel free to update any other wording however you and/or Gobe think is appropriate. I'll also leave updating the ATS doc and the pom.xml up to you.

You can accept the pull request and make additional changes in the opengeospatial repository, or I've given you permission to edit the pull request if you would prefer to make changes there.

[dstenger]

Thank you for updating the pull request. I solved the last two open tasks:

• Update soapui properties
• Update ATS to mark redundant tests
  • I decided to mark tests GetCapabilities.Response.Layer.LegendURL.Correct.Format and GetCapabilities.Response.Layer.LegendURL.Correct.Size with an attention notice instead of removing them as the description of the abstract tests might be helpful. ATS must be refactored in a separate issue.

[dstenger]

Further, I created a new issue for an update of the ATS: https://github.com/opengeospatial/ets-wmts10/issues/83

[ghobona]

This PR has now been installed on the Beta validator.

https://cite.ogc.org/te2/