-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cumbersome experimental conformance reporting suite UX #2205
Comments
Seems like a good area for improvement, thank you for trying out the experimental conformance profile test suite and providing some feedback! /triage accepted I don't think we need to necessarily worry about this for GA however, so I'm not intending to add it to that milestone for now but instead as something to follow up on post-GA: /priority important-longterm Ultimately the experimental suite should in time (as we graduate beyond experimental) replace the current test suite so in theory this gets resolved as a bi-product of normal progression? However if there's some more immediate need or something I've missed here please do let me know. /cc @mlavacca |
Thanks @sunjayBhatia, this would look like a good improvement in usability
+1, even if we should be careful not to lose track of this one, even because when the experimental will become the new standard, most likely we'll be deleting the standard one (or deprecating it), and we should take care of adding this improvement there. |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Currently in Contour we use these conformance suite options to ensure we run all tests by default, but intentionally have to exclude a few that either don't apply or don't pass. In our case, we exclude the Mesh feature and one of the extended support HTTPProxy tests.
Doing this in the experimental conformance suite currently is not as simple as that to get the full report on supported extended features out. Instead you need something like:
It would be great if using the same
suite.Options
setup was possible between the two versions, especially if the current one is eventually replaced by the version that can report conformance results.Notes:
gateway-api/conformance/utils/suite/experimental_suite.go
Lines 114 to 147 in 6d0e6cc
gateway-api/conformance/utils/suite/suite.go
Lines 92 to 105 in 6d0e6cc
The text was updated successfully, but these errors were encountered: