-
Notifications
You must be signed in to change notification settings - Fork 30
Make Error and Fatal functions compatible with testing.T #286
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
Open
sirockin
wants to merge
6
commits into
form3tech-oss:master
Choose a base branch
from
sirockin:sirockin-tb-compatibility
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
52ca7b9
chore: make Error and Fatal functions compatible with testing
sirockin 3d9fb97
Merge branch 'master' into sirockin-tb-compatibility
sirockin eee6067
test: update Fatal/Error tests to take account of more flexible argum…
sirockin 0d29602
Merge branch 'sirockin-tb-compatibility' of ssh://github.com/sirockin…
sirockin ac66ef9
test: add t.Parallel() to subtests
sirockin 6fe4614
Merge branch 'master' into sirockin-tb-compatibility
sirockin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
This would have different logging depending on the number of arguments.
I think if we just add a new log Attr helper that merges a list of errors, we can handle any number of arguments in a consistent way
Uh oh!
There was an error while loading. Please reload this page.
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.
Thanks for the quick review and useful feedback, @nvloff-f3 .
I'm still not exactly clear on what you are looking for though. The original comment said
// Error is equivalent to Log followed by Fail.(consistent with behaviour of testing.T) so I was aiming to get as close to that as possible.Please could you clarify the behaviour you would like to see like to see with:
errorerrorerrorerrorIt would be great if we could create some tests for these scenarios but given the way that concrete logger instances are embedded into
t, that may be difficult to achieve.It could also be argued that rather than introducing a helper to log the arguments, we should amend
Logso that it does what we want then use that in the methods. This would simplify code, make behaviour consistent across these methods and make the original comments forErrorandFatalaccurate. However it would mean that we couldn't forcelogger.Errorto be called if standardprintfarguments were supplied toErrororFatal.Anyway let me know your thoughts and I'll prepare a commit.
Thanks again!