Features for every API in conformance tests #1891
Labels
area/conformance
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
release-blocker
MUST be completed to complete the milestone
Milestone
What would you like to be changed:
Right now we use
StandardCoreFeatures
as a public symbol in our conformance test suite to refer to the features which are required generically across all implementations, andStandardExtendedFeatures
for the extended support level version of that. While "standard" may be correct in this case we need more expressiveness for other feature options:GatewayClass
andGateway
Ultimately we should be in a position where no tests run implicitly, and features must be opted into to run any tests.
Why this is needed:
StandardCoreFeatures
doesn't feel quite right standing alone by itself today and we expect a need for more expressiveness as we complete the work in #1709 as we already have experimental features and will have more in the future.The text was updated successfully, but these errors were encountered: