Re:Suppose I Wanted to Kill a Lot of Pilots (2020)
by bsaul on Tuesday November 09, 2021 @09:47AM
(#29162416)
In my experience, TDD has a bit of a similar effect on your perception on a problem.
By first designing the test that would make the code fail, then making sure it fails, then create the code to have the test pass, you kind of change the way you think about the original problem, and it sometimes helps.
Re:Suppose I Wanted to Kill a Lot of Pilots (2020)
by named-user on Tuesday November 09, 2021 @10:51AM
(#29163329)
Unit tests only catch known failure modes.
TDD only catches assumed known failure modes.
Re:Suppose I Wanted to Kill a Lot of Pilots (2020)
by jerf on Tuesday November 09, 2021 @11:35AM
(#29163897)
That's not a particularly relevant criticism here. The point is that TDD teaches you to think adversarially about your code all the time. The fact that you are not always successful isn't a very interesting criticism; if you don't think adversarially about your code at all you're even less successful. "Testing can't catch all bugs!" is an objection for another discussion.
Re:Suppose I Wanted to Kill a Lot of Pilots (2020)
by rileymat2 on Tuesday November 09, 2021 @12:30PM
(#29164589)
That’s not true, tests also cover happy path, so you can catch failures you had no idea about for instance when running them in a different environment, with a different os, with a different compiler.
It isn't theoretically ideal, but it's a lot better than not thinking this way.