News for hackers. Stuff that matters.
Re:Why Most Unit Testing is Waste [pdf] by helicon on Thursday March 06, 2014 @02:59PM (#7356186)
Isn't this still TDD though?

My understanding was that writing tests first is known as Test-First development which is a subset of TDD. TDD allows you some flexibility to write code first as long as the tests 'drive' the development process?

Re:Why Most Unit Testing is Waste [pdf] by ulisesrmzroche on Thursday March 06, 2014 @03:18PM (#7356304)
No, you shouldn't write code first at all. As soon as you do, you break TDD. You have to write your test first. The practice is pretty dogmatic about this.

The trick to writing a test first is that you have to write what you wish you had. It's kinda like Composed Method in that way.

Re:Why Most Unit Testing is Waste [pdf] by goostavos on Thursday March 06, 2014 @06:31PM (#7357297)
Jesus... All these rules..

I'll stick with the smalltalk adage: code a little. Test a little.

No need for dogma.

Re:Why Most Unit Testing is Waste [pdf] by helicon on Friday March 07, 2014 @07:29AM (#7359827)
I like it ;) Might borrow that one