-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Init conformance test #3400
Init conformance test #3400
Conversation
/kind feature |
374d8f6
to
3fdd22c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking pretty good, just a few smallish comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This conformance test checks the required fields of a succeeded TaskRun created by Tekton Pipelines API.
3e47765
to
71c083d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/test pull-tekton-pipeline-integration-tests |
In tektoncd#3400 we added an initial conformance test, and added a build tag `conformance` to make it so that folks could run just conformance tests if they wanted to. From what I can see it doesn't look like we use this tag at all in our automation, so I want to add it to the tags we use to run our end to end test to make sure this continues working over time. In the long run I think we might want to explore a couple other alternatives for implementing conformance tests, e.g. including making use of our example tests (though those dont express the desired end state), maybe a tool like [kuttl](https://github.com/kudobuilder/kuttl#kuttl) which @chhsia0 has mentioned in preivous working groups, or like the approach that knative seems to be taking via https://github.com/knative-sandbox/reconciler-test But in the short run let's at least make sure this test keeps working :D Also renamed the test to make it a bit more clear what this test is for in case it fails.
Changes
Initialize the conformance test
This conformance test checks the required fields of a succeeded TaskRun created by Tekton Pipelines API.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes