Some tests are too "greedy" and produce skip verdicts about ets-wfs20 HOT 4 CLOSED

You mean that some tests in the Basic conformance class are skipped? For example:

Feature type has no nillable properties: {http://www.interactive-instruments.de/namespaces/demo/cities/4.0/cities}State

It should be possible to ignore feature types for which a test doesn't apply by using a more specialized data provider that filters out inapplicable feature types. In this case, ignore feature types that don't have any nillable properties (there must be at least one, however). The protocol-featureType provider that is often used accepts all feature types for which instances exist, hence the skips.

from ets-wfs20.

Yes, I meant the example you are given above.

Does the "skipping" has any impact on getting certified in the Basic conformance class? If this is not the case it might stay as it is, but if Basic is not accepted because of the "skipping" this should be fixed.

from ets-wfs20.

A skip verdict here should have no bearing on a conformity assessment as long as the test was run and passed at least once. However, since support for this predicate is required for Basic conformance, if no feature type for which instances exist has nillable properties then a fail verdict should result (i.e. unable to test required functionality). This won't happen currently, so the test class PropertyIsNilOperatorTests needs to be modified to detect such a situation.

from ets-wfs20.

If the PropertyIsNil predicate cannot be tested (because no features exist with a nillable property), then an assertion error is thrown with the following message:

Unable to test required capability: PropertyIsNil. No feature type for which instances exist has nillable properties. 

Tests for other required filter predicates could be handled in a similar manner.

from ets-wfs20.