-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reactivate optional tests #47
Comments
I'm stumbling into a problem which may be the same, but could also be related. When running tests from the HTML forms, I can select getFeatureInfo and RESTful tests, and can confirm they are actually run: However, the REST version of the test only comes with the capabilities URL: and indeed the parameters are not exposed in the wmts-auto.xml, which I'm guessing it's used by the REST invocation:), but are instead hard-coded to "off": <ctl:call-test name="wmts:main">
<ctl:with-param name="capabilities-url" select="$capabilities-url" />
<ctl:with-param name="fail-early">off</ctl:with-param>
<ctl:with-param name="include-CommonOperations-tests">on</ctl:with-param>
<ctl:with-param name="include-GetCapabilities-tests">on</ctl:with-param>
<ctl:with-param name="include-GetTile-tests">on</ctl:with-param>
<ctl:with-param name="include-GetFeatureInfo-tests">off</ctl:with-param>
<ctl:with-param name="include-kvp-get-encoding">on</ctl:with-param>
<ctl:with-param name="include-restful-encoding">off</ctl:with-param>
</ctl:call-test> I guess that exposing the parameter requires more than just adding variables in this file... is there documentation explaining how this is done? |
Indeed, adding the parameters in wmts-auto.xml should activate the functionality in the REST interface.
However, there is more work to do if a pull request shall be created:
|
These were deactivated by #28.
#41, for example, asks for GetFeatureInfo tests which were removed.
The text was updated successfully, but these errors were encountered: