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.

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

Merged
merged 1 commit into from
Oct 21, 2020
Merged

Conversation

yaoxiaoqi
Copy link
Member

@yaoxiaoqi yaoxiaoqi commented Oct 16, 2020

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:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

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

Initialize the conformance test

@tekton-robot tekton-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Oct 16, 2020
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 16, 2020
test/conformance_test.go Outdated Show resolved Hide resolved
test/conformance_test.go Outdated Show resolved Hide resolved
@imjasonh
Copy link
Member

/kind feature

@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 16, 2020
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 19, 2020
Copy link
Member

@imjasonh imjasonh left a 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.

test/conformance_test.go Show resolved Hide resolved
test/conformance_test.go Outdated Show resolved Hide resolved
test/conformance_test.go Outdated Show resolved Hide resolved
Copy link
Member

@imjasonh imjasonh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2020
@tekton-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 20, 2020
This conformance test checks the required fields of a succeeded TaskRun created by Tekton Pipelines API.
@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. labels Oct 20, 2020
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2020
@yaoxiaoqi
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

@yaoxiaoqi yaoxiaoqi changed the title conformance test example Init conformance test Oct 21, 2020
@tekton-robot tekton-robot merged commit f1eafbd into tektoncd:master Oct 21, 2020
bobcatfish added a commit to bobcatfish/pipeline that referenced this pull request Apr 1, 2021
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants