Direct WFS is returning different results than OGC Validator

[JohannaOtt]

• a description of the steps to reproduce your issue: I validated this WFS with a local validator instance using validator version 2022.1. This is the test result: KommOne single Test run on 10 55 - 04.04.2022 with test suite Conformance Class Direct WFS.html.zip As I did not know how to interprete for example this error message I repeated the test with the OGC Team Engine validator. I do not get a single error in the "All GML application schemas" tests The test results are also deviating from each other for at least "GML application schemas defining features", "Basic WFS" and "Spatial filter"
• the browser and version used: Firefox 98.0.2
• a screenshot illustrating the problem: see description
• the Test Report (ideally as an attachment to the issue): see description
• the name of the Test that failed: many test results are different from the results in the OGC Team Engine
• the URL of your service: see description

I would expect the results of the INSPIRE Validator conformance class "WFS 2.0 (OGC 09-025r2/ISO 19142) Conformance Test Suite" to be the same as in the OGC Team Engine validator.

[fabiovinci]

Dear @JohannaOtt,

to check the issue, we would need to know which version of the OGC Team Engine validator you used.

Thanks

[JohannaOtt]

@fabiovinci It was the one that is currently available on their production system

So currently: Test Name: wfs20 Test version: 1.36

I just tried again and do still not get an error in the "All GML application schemas" section.

[Dnoack49]

Dear all, we encountered a similar problem validating the following WFS against the WFS 2.0 (OGC 09-025r2/ISO 19142) Conformance Test Suite.

The productive as well as the staging instance report an error regarding the Spatial Filter (here the Test_reports.zip).

I carried out the test with the OGC Team Engine validator (here the Test_reports_CITE.zip) .

Test Name: wfs20 Test version: 1.36 (productive) and 1.37 (staging)

In both, productive and staging system, there was no error but instead the tests were skipped: