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
For long running e2e or functional tests, it would be nice if we could terminate the entire test suite at the point of first failure. I haven't found a way to resolve this yet if there is a way to already, but a flag/parameter to control this behavior internally would make this a lot easier and clearer to implement from an end-user perspective.
My earlier attempts were around trying to use the C.Failed() method to determine whether or not I could panic, but c.Failed doesn't report appropriately inside fixture hooks. Seems kinda like a hack anyway. :)
If you're willing to accept the idea, I can take a stab at a patch.
This would probably be a good idea to set up at the suite level. This would just make it possible for the suite to bail when a test has failed without any extra code in the test itself.
For long running e2e or functional tests, it would be nice if we could terminate the entire test suite at the point of first failure. I haven't found a way to resolve this yet if there is a way to already, but a flag/parameter to control this behavior internally would make this a lot easier and clearer to implement from an end-user perspective.
My earlier attempts were around trying to use the C.Failed() method to determine whether or not I could panic, but c.Failed doesn't report appropriately inside fixture hooks. Seems kinda like a hack anyway. :)
If you're willing to accept the idea, I can take a stab at a patch.
/cc @unclejack
The text was updated successfully, but these errors were encountered: