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

[robinhoutmeyers]

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:

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]

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]

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]

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]

I also encountered a similar issue during a beta test for #66. Steps to reproduce:

• Start a WMS Client beta test session
• Open https://dev.luciad.com/portal/packed-samples/ria/dataformats/index.html?webgl&reference=epsg:4978
• Click on "Connect to..." and select "WMS"
• Fill in the proper GetCapabilities URL; e.g. (replace the number 33 with the actual number): https://cite.ogc.org/te2/monitor/33?REQUEST=GetCapabilities&SERVICE=WMS
• Click Next, select the Basic polygons layer and click Next again.

=> 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]

@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]

Noted, thanks!

[dstenger]

@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.