Thank you for reporting.

I can reproduce the behavior and, indeed, the logged request in HTML report returns HTTP status code 403 which is valid for this test.
We will do further investigation.

Workflow of reproducing HTTP Status 403 (using Firefox plugin RESTED):

• POST https://contenido.ign.es/wfs-inspire/unidades-administrativas

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="10" service="WFS"
                version="2.0.0">
   <wfs:Query xmlns:ns84="http://inspire.ec.europa.eu/schemas/au/4.0"
              typeNames="ns84:AdministrativeUnit">
      <fes:Filter xmlns:fes="http://www.opengis.net/fes/2.0">
         <fes:BBOX>
            <fes:ValueReference xmlns:tns="http://www.opengis.net/gml/3.2">tns:description</fes:ValueReference>
            <gml:Envelope xmlns:gml="http://www.opengis.net/gml/3.2" srsName="urn:ogc:def:crs:EPSG::4258">
               <gml:lowerCorner>27.62 -18.17</gml:lowerCorner>
               <gml:upperCorner>43.8 4.33</gml:upperCorner>
            </gml:Envelope>
         </fes:BBOX>
      </fes:Filter>
   </wfs:Query>
</wfs:GetFeature>

However, the response body is empty which would also lead to a failing test.

Thus, it might be that the response originates from a proxy server and not the application itself.

Thanks, @dstenger. As we discussed internally, I tested with Postman and I get a HTTP 200 response with feature data. Looking at the log, it seems that the Test Suite also receives a HTTP 200 response. The test expects either a HTTP 400 or 403 response.
We will update the error message with the actual HTTP response code for a better understanding.

We enhanced the error message (will be installed on the beta test engine soon: https://cite.ogc.org/te2/). Now, when I test your service, it will report Unexpected HTTP status code. Expected '400' or '403', was '200'. Can you please check why your service responds with a 200 for the request below?

Thank you for reporting.

I can reproduce the behavior and, indeed, the logged request in HTML report returns HTTP status code 403 which is valid for this test. We will do further investigation.

Workflow of reproducing HTTP Status 403 (using Firefox plugin RESTED):

• POST https://contenido.ign.es/wfs-inspire/unidades-administrativas

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="10" service="WFS"
                version="2.0.0">
   <wfs:Query xmlns:ns84="http://inspire.ec.europa.eu/schemas/au/4.0"
              typeNames="ns84:AdministrativeUnit">
      <fes:Filter xmlns:fes="http://www.opengis.net/fes/2.0">
         <fes:BBOX>
            <fes:ValueReference xmlns:tns="http://www.opengis.net/gml/3.2">tns:description</fes:ValueReference>
            <gml:Envelope xmlns:gml="http://www.opengis.net/gml/3.2" srsName="urn:ogc:def:crs:EPSG::4258">
               <gml:lowerCorner>27.62 -18.17</gml:lowerCorner>
               <gml:upperCorner>43.8 4.33</gml:upperCorner>
            </gml:Envelope>
         </fes:BBOX>
      </fes:Filter>
   </wfs:Query>
</wfs:GetFeature>

However, the response body is empty which would also lead to a failing test.

Thus, it might be that the response originates from a proxy server and not the application itself.