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

Run TestReconcileTimeouts as separate tests ⏰ #3030

Merged
merged 1 commit into from
Jul 30, 2020

Conversation

bobcatfish
Copy link
Collaborator

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:

  • Includes tests (if functionality changed/added)
  • [n/a] 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)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

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

NONE

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.
@bobcatfish bobcatfish added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jul 29, 2020
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Jul 29, 2020
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 29, 2020
c := testAssets.Controller
clients := testAssets.Clients
t.Run(tc.name, func(t *testing.T) {
d := test.Data{
Copy link
Member

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 🤔

Copy link
Member

@pritidesai pritidesai Jul 29, 2020

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

@pritidesai
Copy link
Member

/test pull-tekton-pipeline-integration-tests

@pritidesai
Copy link
Member

/approve

@tekton-robot
Copy link
Collaborator

[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 /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 Jul 29, 2020
@dlorenc
Copy link
Contributor

dlorenc commented Jul 30, 2020

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2020
@tekton-robot tekton-robot merged commit 3fc7c03 into tektoncd:master Jul 30, 2020
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/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants