FRESH

Hacker News

The Big TDD Misunderstanding

40 points by WolfOliver

by viraptor

1 subcomments

It's nice that this reminder surfaces from time to time. Hopefully there are a few lucky 1/10000ths today.
I'd just add some nuance to:
> If you cannot reach the untested lines with the public interface of your software, maybe you can just delete those lines. Do not reach for stubs/mocks to achieve 100% test coverage, try to find a scenario of how to run through these branches by using the API from a realistic point of view.
Sometimes you need a few mocks for exceptional situations. You're not going to fill up your disk just to check that ENOSPC, or try to race the test with bringing down an interface to reproduce network timeouts.

by somewhereoutth

1 subcomments

I would add that human interfaces need to be tested by humans (preferably not your paying customers), machine interfaces by machines.

by MoreQARespect

0 subcomment

by andrewstuart

1 subcomments

Hopefully AI has killed TDD dead dead dead.
TDD is one of the worst concepts ever concocted by the software industry right up there with UML.
It’s all very ThoughtWorks.
One of the very best things to come out of AI development is the extent to which it sends TDD to the ninth level of hell.