3 ms·

I agree, but the tests are in the order of minutes (sometimes hours), not your typical unit tests. That's basically why it uses soft assertions, it's costly to

I agree, but the tests are in the order of minutes (sometimes hours), not your typical unit tests. That's basically why it uses soft assertions, it's costly to run. Ideally you'd still want tests with a single assertion/target state, but it's hard to write it that way. We also do have this conditional test hierarchy, but again it's hard to properly define when the system under test behaves unexpectedly...

r0s 6y ago
> it's hard to properly define when the system under test behaves unexpectedly... I feel your pain. I think at that point it's good to look deeper and ask if exceptions are being properly thrown, as I try to call for in the final section on Exceptions. You can't plan for everything.