-
Notifications
You must be signed in to change notification settings - Fork 596
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
Subscription Conformance Tests completion #5782
Comments
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
Who can add more details of this issue? |
Yep, edited the issue with more context =) |
I'm working on broker's conformance tests. |
Of course tomorrow morning I'll check it out :) thanks for the ping @daisy-ycguo |
/good-first-issue I'd recommend to split the solution for this issue in multiple PRs, one for each scenario |
@pierDipi: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
@gabo1208 I am working on Broker Conformance tests and Channel Input tests |
/assign |
/assign |
@gabo1208 shall I take the responsibility of filling all the todo's there into 2 pr's addDataPlaneDelivery and observability |
Ideally yes, but any progress is appreciated! |
Problem
We don't have all the MUST clauses in the Subscription spec covered by tests in the project, for example:
https://github.com/knative/eventing/blob/792f56ddb5e2328005149e7af571be6ca667cd89/test/rekt/features/channel/data_plane.go lots of
todo
in.must
clauses in this file.Same with the other CRDs (Subscription, Broker, Trigger)
Persona:
Developers
Exit Criteria
Have at least one test per MUST clause from the Subscription specs
Additional context (optional)
This is part of the Conformance GA plan
The text was updated successfully, but these errors were encountered: