opengeospatial / ets-wms-client13

Repository for the Exectutable Test Suite for WMS Client 1.3.X
Other
1 stars 3 forks source link

The WMS Client test does not put "Perform GetMap request for all the layers" on passed when all child tests have been passed #68

Closed robinhoutmeyers closed 7 months ago

robinhoutmeyers commented 1 year ago

I executed the WMS Client test in combination with our desktop WMS client software based on LuciadLightspeed. It works and it seems all child tests have been passed, but the "Perform GetMap request for all the layers" parent node seems to remain on the failed state.

Here is a screenshot of the test result:

image

As you can see, all tests below "Perform GetMap request for all the layers" are passed, but the parent node remains failed. I can consistently reproduce this.

dstenger commented 1 year ago

Thank you for reporting. I am also able to reproduce the behavior when testing with QGIS. However, when finishing the test session and viewing the report, I cannot see any tracked failure. Thus, this just seems to be a display error. Can you please check and confirm if this also applies to your use case?

robinhoutmeyers commented 1 year ago

Indeed! The summary of results doesn't shown any failure after finishing the test session and viewing the report; only the test overview this shows it as shown in my screenshot, but I guess this is not a problem to request compliancy.

dstenger commented 1 year ago

I agree, it should be no problem to request compliance. However, I leave the issue open to further investigate why the display is not correct.

robinhoutmeyers commented 11 months ago

I also encountered a similar issue during a beta test for https://github.com/opengeospatial/ets-wms-client13/issues/66. Steps to reproduce:

=> although the test session console and the test results (after stopping the test) will recognize the fact that a GetCapabilities and GetMap requests were received, the display during the test is never updated.

ghobona commented 10 months ago

@robinhoutmeyers Please note that since the issue is acknowledged as a bug in the ETS, you can proceed with submitting your product for compliance certification.

robinhoutmeyers commented 10 months ago

Noted, thanks!

dstenger commented 10 months ago

@robinhoutmeyers We created a pull request for the problem mentioned in the description of the issue. However, the second issue reported here seems not to be related to the first one. Thus, we moved it to a separate issue: #73. We are already working on the new issue.