Of course I did but like any other process if there has to be complete adoption the benefits need to be clearly visible and significant. The problem with pure T

Of course I did but like any other process if there has to be complete adoption the benefits need to be clearly visible and significant. The problem with pure TDD (and remember that's what I am talking about - writing / updating tests before writing any code), is that there are diminishing returns as soon as the code base becomes a certain size. In fact, at some point the costs flip around to be higher than the benefits (ie: updating code before tests becomes significantly more efficient than the other way around). In my experience, it has always been easier for multiple developers working on a code base to write the tests once the implementation has been fleshed out and a significant portion of it is 'ready'.