Handle failures at tearDown()
#20
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
Checklist: - handle failures at tearDown() 👈🏼 --- Output: ➜ python3 src/test_case_test.py 6 run, 1 failed
This class will implement the scenario of a test case with a broken tearDown() method, which throws an exception every time it's ran. Checklist: - handle failures at tearDown() 👈🏼 --- Output: ➜ python3 src/test_case_test.py 6 run, 1 failed
kaiosilveira
force-pushed
the
bonus/handle-failures-at-teardown
branch
from
13fcc30
to
30c9a78
Compare
Exceptions at tearDown() are now captured and handled properly. Checklist: - handle failures at tearDown() ✅ --- Output: ➜ python3 src/test_case_test.py 6 run, 0 failed
kaiosilveira
force-pushed
the
bonus/handle-failures-at-teardown
branch
from
30c9a78
to
e85ae13
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.
Bonus: handle failures at
tearDown()Our goal in this PR was to make sure that exceptions in the
tearDown()step were caught and reported back to the test client. We accomplish that by wrapping the call to this method with atry/exceptblock.Closes #19