Re: Suggestion, advice on TDD adoption

> On Apr 6, 2016, at 4:57 PM, Keith Ray [email protected] [testdrivendevelopment] <[email protected]> wrote:
> 
> It really really helps to have a coach working with your team and its code.
> 

This is really a key. Without a coach, you are going to wind up trying things, not understanding why they don’t work, and largely reinventing a lot of practices. A coach can save you an incredible lot of time. You can get some of it from books such as Robert Martin’s Clean Code <http://www.barnesandnoble.com/w/clean-code-robert-c-martin/1101628669> (and other books in the series), but a good coach is still much better.

> 
> On Apr 6, 2016, at 4:53 AM, [email protected] <mailto:[email protected]> [testdrivendevelopment] <[email protected] <mailto:[email protected]>> wrote:
> 
>> We have recently started using TDD. We have gone through the training, learned some of the TDD good practices/challenges, using junit, mockito tools/framework etc. Since its an early start to the journey, I would be glad to hear some practical advice from folks here, some of the DOs and Dont's, tips and tricks etc. We are going to have a bumpy ride, especially with exisitng code, so it will really help if we can hear from experinced people. 

-----------------
Author, Getting Started with Apache Maven <http://www.packtpub.com/getting-started-with-apache-maven/video>
Author, HttpUnit <http://www.httpunit.org> and SimpleStub <http://simplestub.meterware.com>

Come read my webnovel, Take a Lemon <http://www.takealemon.com>, 
and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!