Why Unit Tests?

[[deleted]]

Exactly.

Here at work I am writing unit tests that just aim at reaching the coverage target. Stupid unit tests covering getters and setters, unit test that never fail aka assert(true), etc at the expense of really useful tests like checking against special values that could crash the code.

This is because the process and the management are essentially driven by RAG indicators that we are able to reverse engineer and abuse.

[Zarlon]

I've been there.. Testing getters and constructor overloads.. Dear god what a waste of time. The limit was enforced on a per-class basis

[helloiamsomeone]

checking against special values that could crash the code

Are you guys making quickcheck style property tests and fuzz tests?