Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[1.0] Conformance testing for parallels.flows.knative.dev #4939

Closed
5 tasks
n3wscott opened this issue Feb 22, 2021 · 4 comments
Closed
5 tasks

[1.0] Conformance testing for parallels.flows.knative.dev #4939

n3wscott opened this issue Feb 22, 2021 · 4 comments
Labels
area/test-and-release Test infrastructure, tests or release kind/good-first-issue Denotes an issue ready for a new contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone
Backlog

Comments

@n3wscott
Copy link
Contributor

The following work needs to be validated for parallels.flows.knative.dev to be ready for 1.0:

  • parallels.flows.knative.dev is fully documented in the Eventing Spec document.
  • parallels.flows.knative.dev has a 100% coverage conformance test based on the spec.
    • Conformance tests are documented and vendor-able for downstream implementors to validate their implementations.
    • Conformance tests are written with the various levels of spec compliance (MAY/SHOULD/MUST) and pass/fail given those constraints.
  • Documents how to use the conformance test outside Eventing.

Please see https://github.com/knative-sandbox/reconciler-test for more details on conformance testing.
Blocked on knative-extensions/reconciler-test#100
@lberk lberk added this to the Backlog milestone Mar 1, 2021
@slinkydeveloper
Copy link
Contributor

Any existing tests already covering the subject should be ported to reconciler-test

@slinkydeveloper slinkydeveloper added kind/good-first-issue Denotes an issue ready for a new contributor. area/test-and-release Test infrastructure, tests or release labels Mar 10, 2021
@github-actions
Copy link

github-actions bot commented Jun 9, 2021

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2021
@n3wscott
Copy link
Contributor Author

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/test-and-release Test infrastructure, tests or release kind/good-first-issue Denotes an issue ready for a new contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@lberk @slinkydeveloper @n3wscott @knative-prow-robot