-
Notifications
You must be signed in to change notification settings - Fork 105
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
[env] Don't run next assess when failNow is called #391
[env] Don't run next assess when failNow is called #391
Conversation
When writing tests, this allows the writer to control whether the test should continue running the next assess when a failure occurs. Basically, they can chose between using `t.FailNow()` or `t.Fail()` depending on if the failure should stop the test or not. It works independently from the `-fail-fast` flag specific to the framework and allows a more granular control on test failures.
Hi @Fricounet. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/ok-to-test
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 for this change. Will let @harshanarayana take a look.
/lgtm
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Fricounet, harshanarayana 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 |
/retest |
What type of PR is this?
/kind bug
What this PR does / why we need it:
When writing tests, this allows the writer to control whether the test should continue running the next assess when a failure occurs. Basically, they can chose between using
t.FailNow()
ort.Fail()
depending on if the failure should stop the test or not. It works independently from the-fail-fast
flag specific to the framework and allows a more granular control on test failures.Which issue(s) this PR fixes:
Fixes #386
Special notes for your reviewer:
I tried to add a new test for this case but couldn't find a way to make it work. Since
failNow
is called, the test fails and I couldn't find a way to expect a test to fail in go 😅. Happy to add one if someone has an idea on how to do it though.Code to reproduce
You can use the following code to illustrate what I'm trying to solve
Does this PR introduce a user-facing change?
Additional documentation e.g., Usage docs, etc.: