test: refactor to use assert pkg instead of t.Fatal #2880
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexandear
force-pushed
the
test/refactor-to-use-assert
branch
2 times, most recently
from
268dbf9
to
eff126a
Compare
Signed-off-by: Oleksandr Redko <[email protected]>
alexandear
force-pushed
the
test/refactor-to-use-assert
branch
from
eff126a
to
e4073ad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors tests:
if err != nil { t.Fatal(err) }withassert.NilError(t, err)for consistency with other tests.forbidigorules to forbid usingt.Fatalin tests.Using
t.Erroris acceptable. Sometimes tests need to report failure and continue execution.