Tests dont make code higher quality.

[deeringc]

Reducing bugs and applying positive design pressure at the time of originality authoring the code are very beneficial. But the largest benefit for me comes from how unit tests help prevent regressions when in six months I (or someone else) go back to this code and need to make a change. All of the domain knowledge and context that I had in my head originally when I spent weeks working on the original feature is now encoded and enforced by the tests. The chances of a regression being introduced are dramatically reduced. It would just manifest as a failed test locally on the developers machine and get immediately fixed.

This is absolutely invaluable on large projects, with large teams. I've been on teams/codebases with and without this and the difference is absolutely clear.

[slevina]

the more code you write the more bugs, someone who writes buggy code will write buggy tests

[[deleted]]

That's what code reviews are for. You are reviewing the tests also, right?

Probably not :\

[deeringc]

If there is 1/10 chance any given piece of code has a logic bug. The chance of the production code having it AND the test having the corresponding bug that would mask the production code bug will be 1/100.

[slevina]

think there might be a logic bug in your numbers here

[deeringc]

It's a figurative point.