You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like this library but it seems to require lot of boilerplate code to get running.
Can we have a class based approach as well to the existing approaches?
What do you think about the following way?.
classTestDescribeTest():
defcase_one(self, fixture1, fixture2, fixture3):
returninput, output, errdefcase_two(self, fixture2, fixture3):
returninput, output, errdeftest_function(self, input, output, err):
# test body
I know I can just put this inside generate_tests to parameterize the test, but not sure, how to pass the parameters from the case functions and make the case functions behave like fixture functions. What are your opinions?
The text was updated successfully, but these errors were encountered:
I agree with you - this is why I am in the process of making the experience closer to pytest. (See #90 )
This should happen within one or two weeks, so I suggest that we take this conversation again when it (and the associated new readme) is done. Until then, you can put the case functions in a dedicated module (I use the convention test_xxx_cases.py when your test file is test_xxx.py, it will even be the default in v2)
Sorry for delaying, and thanks for your patience !
I really like this library but it seems to require lot of boilerplate code to get running.
Can we have a class based approach as well to the existing approaches?
What do you think about the following way?.
I know I can just put this inside generate_tests to parameterize the test, but not sure, how to pass the parameters from the case functions and make the case functions behave like fixture functions. What are your opinions?
The text was updated successfully, but these errors were encountered: