To be fair, there's no shortage of high level advice on how to write good tests (e.g. "each change in the code should break just one test"), but it's hard to find examples of how to do so in practice (unless you're writing yet another calculator app)...
>Hard to argue with this logic:
> ...
Agree
> but it's hard to find examples of how to do so in practice
yeah, I think that it is because every architecture/design/component/layer seem to need a different testing approach. You really have to look at the specific case to come up with a good strategy.
1. Poorly designed unit tests are a waste.
2. Most code is poorly designed.
3. Therefore most unit tests are a waste.
To be fair, there's no shortage of high level advice on how to write good tests (e.g. "each change in the code should break just one test"), but it's hard to find examples of how to do so in practice (unless you're writing yet another calculator app)...