-
Notifications
You must be signed in to change notification settings - Fork 2
#55 Fixed the empty input bug #57
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
Conversation
_ = StandaloneMockContext(inp, meta_data) | ||
# There is nothing to test here apart from successful creation of the | ||
# context object. This internally has some checks that need to be passed. | ||
pass |
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.
Maybe the test could assert that the constructor does not raise an exception?
https://stackoverflow.com/questions/4319825/python-unittest-opposite-of-assertraises
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 understand why it is so important to make a distinction between a failure and an error. Either way, pytest will point out where the problem is. If you convert an exception to an assert failure you are more likely to hide the actual cause of the error.
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.
Maybe you can enlighten me.
Co-authored-by: Christoph Kuhnke <christoph.kuhnke@exasol.com>
closes #55
closes #56
All Submissions: