[rocqua]

Assertions triggering in integration tests are different from unit tests. They don't involve writing mocks. They are generally closer to the code, especially with design by contract, so they are more likely to be fixed during a refactor. They encode what you believe your code should do more directly. And they can be used as a basis for formal verification.

[_0ffh]

Hey, I'm arguing in favour of contracts and assertions here... XD

I even considered formal verification, if under another name.

Ed.

I think I hit a posting limit. After reading dataflow's answer to gp I think I interpreted ggp differently from both of you.

I meant quite literally neither assertions nor unit tests prevent you from breaking things. Of course they'll help you to catch those mistakes before release. I didn't think that counts as prevention.