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
r10 does not send mandatory SERVICE parameter #11
Comments
Service parameter is not mandatory for GetMap requests. |
See comment from opengeospatial/ets-wms-client13#5 |
This could have a massive impact on every testcase through all the ETSs, as IMHO every testsuite has a related test, to check if for instance a GetMap request is working without that parameter. |
@segoerke, talking to OGC staff, it seems that the complaint is valid. We should not enforce the SERVICE parameter. Can you please check how big is the impact? |
@segoerke, so if we are going to keep the rule as it is, can you please provide better information/guidance for the tester, inside the tests and when giving back the results? Thank you very much! |
What do you mean with better guidance? We could add a hint to the description of the WMS 1.3.0 ETS. Or a precondition test could be added checking if a GetMap request can be executed without the service parameter (but wouldn't this be too much overhead?). |
Add information in the section about how to run the test. |
Please add some information here: /ets-wms13/src/site/markdown/index.md |
Hint about missing service parameter was added and is provided by pull request #31. |
The pull request (#31) was tested successfully, merged to the master branch and will be part of the upcoming release. |
When testing my WMS for OGC conformity using the testdataset, I do not
see the "large diamond". But the reason seems to be a bug in the testengine:
src does not send the mandatory SERVICE parameter:
I guess this is a bug in the r10 of WMS 1.3 testsuite in team engine 4.0.5
Marco
The text was updated successfully, but these errors were encountered: