News for hackers. Stuff that matters.
Re:Where TDD Fails by andrewflnr on Tuesday March 05, 2013 @09:52PM (#5329046)
Re 1, GP is talking about time to develop features, including writing tests, not to actually run the tests.
Re:Where TDD Fails by Glide on Tuesday March 05, 2013 @10:49PM (#5329206)
That may or may not be valid depending on what one considers "done" in the context of a project.

My team considers a feature done when it goes through QC and business analysis.

I personally find it nice to just hit a couple of hotkeys instead of working through the application itself in order to test functionality. It does save me time because I want to ensure that the feature works and I have to devote less cycles to fix some small thing I missed when running the real app as opposed to tests.

Re:Where TDD Fails by boyter on Wednesday March 06, 2013 @01:25AM (#5329704)
As am I. In my sample app its faster to write the feature and the tests and run those then to spin everything up and see it working. I have had the same experience in large Java applications as well.