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
When you have a test that needs to run multiple times, or simply includes an iteration of some sort, it is often useful to know at which iteration an assertion failed. Currently the only way to include that data with because:
The issue with that workaround is that each "test" needs to happen serially, as I'm using a test runner that runs tests in parallel. What do you mean by software assertions?
When you have a test that needs to run multiple times, or simply includes an iteration of some sort, it is often useful to know at which iteration an assertion failed. Currently the only way to include that data with
because
:It would be nice if there was a simple way of including arbitrary data along with an exception, maybe something like this:
Or perhaps a middle-ground would be to allow
because
to be used likeformat
:The text was updated successfully, but these errors were encountered: