-
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
Run TestReconcileTimeouts as separate tests ⏰ #3030
Conversation
I noticed that these tests are setup to run as separate test cases but weren't using the t.Run functionality that lets them actually be treated as separate test cases. Added t.Run so that one test case failing will not prevent the others from running and failures will be reported separately.
c := testAssets.Controller | ||
clients := testAssets.Clients | ||
t.Run(tc.name, func(t *testing.T) { | ||
d := test.Data{ |
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.
we need similar refactoring here 😿, the ones we did in PR #2876 and may be share some of the common functions 🤔
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.
When I work on separating common functions like we discussed in PR #2876, I will try and see if its possible to refactor taskrun_test.go
/test pull-tekton-pipeline-integration-tests |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pritidesai 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 |
/lgtm |
Changes
I noticed that these tests are setup to run as separate test cases but
weren't using the t.Run functionality that lets them actually be treated
as separate test cases. Added t.Run so that one test case failing will
not prevent the others from running and failures will be reported
separately.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
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