Test Driven Development? You've got to be kidding me...

Re:Test Driven Development? You've got to be kidding me... by phzbOx on Saturday September 24, 2011 @10:52AM (#3033341)

Still, starting with testing helps so much to create modular design because it forces you to write clear/clean interfaces between them.

My workflow is usually:

  1. Write the tests and design the module/class/whatever in the same time.
  2. Code it. (Repeat)

Although, I rarely write unit tests in TDD; only tests providing a high level design view (Such as functional or integration tests).

[ Parent | on HN ]

Re:Test Driven Development? You've got to be kidding me... by peteretep on Saturday September 24, 2011 @10:59AM (#3033361)

And perhaps I didn't make my points clearly enough in the article; I was really trying to differentiate between the Test-Driven Development dogma as a panacea for all development problems ever, and developers writing tests first where it makes sense to do that.

[ Parent | on HN ]

Re:Test Driven Development? You've got to be kidding me... by cbs on Saturday September 24, 2011 @01:41PM (#3033810)

>And perhaps I didn't make my points clearly enough in the article

You made them more than clear. People just want to argue the headline. Good post BTW I'm subscribing to your RSS feed.

[ Parent | on HN ]

Re:Test Driven Development? You've got to be kidding me... by bigbango on Monday September 26, 2011 @04:29AM (#3038073)

I never understood why people can't write well designed modular code without writing the test first.

Tests should never dictate the design of an application.

[ Parent | on HN ]