Project Implementation estimates with TDD -


are there guidelines when quoting estimates projects/tasks involving tdd?

for example, when compared normal development of task taking 1 day complete, how more should tdd driven task take? 50% more time or 70% more time? there statistics available, assuming developer versed language , test framework?

the difference high @ first, decreases experience, factor

the difference in implementation time between conventional coding , tdd decline developer becomes better @ tdd. tdd beginners, , intermediates, caught-up deciding tests write and/or write more tests end being thrown out after refactoring. experience, tdd'er become more efficient, become better , quicker @ choosing tests write

i'm not sure absolute lower limit of ratio of conventional tdd is. i'd guess 1:1.5, can't believe developers can ever test-drive code fast write code, less write code write tests.

and others have said, significant payoff time spent doing tdd debugging time vastly reduced test-driven code.


Comments

Popular posts from this blog

javascript - Enclosure Memory Copies -

php - Replacing tags in braces, even nested tags, with regex -