-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
TST: better assertion messages on test failures (GH4397) #4430
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
Merged
Merged
Changes from all commits
Commits
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
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.
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.
I don't think this is as useful as what we had previously. It needs to raise when one of the components does not have an attribute (e.g., it's the wrong type altogether or something weird has happened). Further, if you do
hasattr
orgetattr
, it's not exactly equivalent to trying to get the attribute and defaulting to None otherwise. (and also I thinkgetattr
ignores any exception that occurs when trying to get it). So, I think it's better to add an assert_equal that takes an argument which explains. e.g.Where
assert_equal
is:Plus, this means that the Exception that will bubbles up if something goes wrong will not be on
assert_attr_equal
but will instead be on the lineassert_equal(left.column.dtype, right.column.dtype, msg)
and you'll get the nice error message about not having an attribute and you'll see it's on the column...much easier to debug.To illustrate the difference, check out this small example:
And if you just change the
getattr(left, attr, None)
togetattr(left, attr)
, you still lose the nicer error output because the actual error line will readgetattr(left, attr)
rather thanleft.column.dtype