Have tests inspect an exception's e.value instead of just e as pytest 5.0.0 changed its behavior #418
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
|
I've resubmitted this with just the fix to the pytest 5.0.0 problem. I'm sorry if I did any confusing git things; I've spent 13 years using Perforce and learning Git has been slow going :) |
pytest 5.0.0 no longer displays the custom text with str(e)
|
Thank you! I took the liberty of rebasing your changes to the current master and squashing the commits to simplify the history. |
matteobachetti
approved these changes
Jul 2, 2019
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 fix addresses twongCMU#1 in which the some unit tests fail under pytest 5.0.0. This version changed an exception to only show the exception type and not the custom text; that info is in e.value now.