Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle exceptions at tearDown() #19

Closed
kaiosilveira opened this issue Mar 19, 2023 · 0 comments · Fixed by #20
Closed

Handle exceptions at tearDown() #19

kaiosilveira opened this issue Mar 19, 2023 · 0 comments · Fixed by #20
Assignees
@kaiosilveira
Labels
bonus challenge Bonus points presented in the book

Comments

@kaiosilveira
Copy link
Owner

kaiosilveira commented Mar 19, 2023 •
edited
Loading

Currently, if we have a problem in the tearDown() step, our code will just fail silently. We need to expose this failure and report it back to the test client.
@kaiosilveira kaiosilveira self-assigned this Mar 19, 2023
@kaiosilveira kaiosilveira added the bonus challenge Bonus points presented in the book label Mar 19, 2023
@kaiosilveira kaiosilveira mentioned this issue Mar 19, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaiosilveira kaiosilveira

Labels
bonus challenge Bonus points presented in the book
Projects
No open projects
TDD part II: The xUnit example - implementation roadmap
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle failures at tearDown() kaiosilveira/tdd-xunit-example
1 participant
@kaiosilveira