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
The thought has certainly crossed my mind, but I haven't really found any good use cases for it. Not that I've really looked all that much. Requiring a single assertion per test encourages simple tests, and I think your specific case here is a good example of that since it's trying to test two different properties at once.
I think it's good practice to design your tests around the properties you'd like tested instead of just "coverage".
After some more thought and experience, I think enforcing a single assertion per test is still the right approach. Support for generating tests based on a set of test cases was added with testAll in #12, however, and might relieve some of the need you feel for combinators.
I'll close this for now, reopen if you find a scenario where you think the current tools are insufficient.
There is a lot of cases where I want to write something like this:
So we can combine two assertions into one. Do you think this is possible? @glennsl
Thanks!
The text was updated successfully, but these errors were encountered: