An External Replication on the Effects of Test-driven Development [pdf]

Re:An External Replication on the Effects of Test-driven Dev... by crdoconnor on Wednesday October 19, 2016 @04:11AM (#12741991)

I have the same positive experience as both of the above commenters. I've found that there are many other variables which can change its effectiveness though:

* The type of code I'm working on

* How well I remember/understand the full requirements.

* How much of the testing framework is built already and how much I have to build.

* The type of test I'm writing.

* How new the project is.

[ Parent | on HN ]

Re:An External Replication on the Effects of Test-driven Dev... by collyw on Wednesday October 19, 2016 @06:48AM (#12742656)

Yes, TDD seems to involve having a decent idea of the requirements (very un-agile). Many projects are making it up as they go along and iterating to a reasonably correct outcome.

[ Parent | on HN ]

Re:An External Replication on the Effects of Test-driven Dev... by crdoconnor on Wednesday October 19, 2016 @08:48AM (#12743249)

It means having a clear idea about the requirement you're implementing at that point in time (not un-agile). It doesn't mean that you have to create a big set of requirements up front (un-agile). You can just pick a story, convert it into a test and implement the code, rinse and repeat.

Writing the test also gives you a second chance to think deeply about the requirement and fix any problems with it before wasting time implementing the wrong thing.

[ Parent | on HN ]