4 ms·
> If the test is in a invalid state then you can't trust soft asserts that pass. Agreed, which is why I suggest designing each test for a single target state.
by r0s 6y ago
> If the test is in a invalid state then you can't trust soft asserts that pass.
Agreed, which is why I suggest designing each test for a single target state.
That target may then legitimately benefit from multiple assertions, and you have the same problem.
- rightbyte 6y agoYe at-least for projects with many developers involved. My experience is that tests that tests too much makes QA collapse when the original authors of the tests are gone and no-one know what tests are actually testing implementation or spec. I use #ifdef:s to enable "intermediate state" and implementation asserts usually to mark them as development tests.