-
Notifications
You must be signed in to change notification settings - Fork 222
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
[TEP-0079] Catalog Automated Testing and Tekton Dogfooding #914
[TEP-0079] Catalog Automated Testing and Tekton Dogfooding #914
Conversation
/kind tep |
1 similar comment
/kind tep |
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
/assign @dibyom |
@vinamra28 please approve the proposal instead of |
|
||
#### Community Catalog Template Testing Infrastructure | ||
|
||
The test infrastructure in the plumbing repo is designed for all `tektoncd` projects, which may not fit a Community Catalog repo's needs and may be too complicated for the authors to start with. To encourage Community Catalog authors to set up automated tests for their catalogs (using Tekton!), we propose to provide a template repo in the `tektoncd-catalog` GitHub org for Community Catalog authors to follow. This tutorial-like template should contain the **simple and minimum** required setup for the automated build tests and integration tests, guiding Community Catalog authors to achieve the same testing functionality as the Verified Catalogs using vanilla Tekton primitives. |
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.
Are we suggesting each project have their own eventlistener?
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.
I think the choice is on the community catalog authors? We just provide an example to them to start with. But I would personally use the same el for multiple projects.
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.
Thank you @QuanZhang-William!
There are some open questions around the testing strategy:
- how often would we run the integration tests? nightly? on PRs only?
- which Tekton versions would we test these resources against? nightly release? latest release? minimum compatible version?
@bobcatfish discussed some ideas here: #170
/assign
putting a hold so that it's not accidentally merged on the first approval because it already has an lgtm /hold |
cfff349
to
60d7621
Compare
Thanks @jerop for the link! I have added 2 sections under the Integration Test section, talking about the nightly integration test and PR merge integration test respectively, including the |
60d7621
to
557fb7c
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.
Thank you @QuanZhang-William!
/hold cancel @dibyom @vinamra28 please take a look |
This commit updates the "Automated Testing and Dogfooding" section of TEP-0079, which adds the testing strategy proposal for the Verified Catalogs and a testing infra template for Community Catalogs.
557fb7c
to
028a235
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom, jerop, vinamra28 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 |
Approved during API WG |
This commit updates the "Automated Testing and Dogfooding" section of TEP-0079, which adds the testing strategy proposal for the Verified Catalogs and a testing infra template for Community Catalogs.
This commit also update the tep from
proposed
toimplementable
🥂