The Startup
Published in

The Startup

Test Driven Development — An Opinion

Photo by Antoine Dautry on Unsplash

Bad Designs and TDD

So were I to follow the TDD architecture I would have to constantly revisit my tests, review all of them, revising them to match my discoveries.

Writing tests up-front

Here is what TDD looks like to me:

write the TDD tests

begin implementation

discover an unanticipated consideration

rewrite the tests

continue implementation

goto 3 over and over and over …

(actually more like item 150) all tests pass

send to QA

Don’t test your own code!

In summary

Read any advocacy of TDD and it will always boil down to an argument for testing itself, which nobody argues against. It never makes a case for writing tests before implementation.

There is no rationale for writing tests before implementation.

That is absurd.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store