TDD Best Practices?

[nelsonic]

Yesterday we got the following email thanking us for the Learn TDD tutorial: (anonymised for privacy)

We increasingly get "thank you" emails from random strangers and that's great.
(we don't need people to thank us for our free tutorials, because the motivation is intrinsic,
but it's nice when people thank us because it reminds us that open source docs helps everyone!)

The reason I'm sharing this email is simple: it has a specific request for a call/session to go through TDD Best Practices with their team. This sort of "remote consulting" is exactly what we intend to do once @home is up-and-running. We will even have a dedicated "studio" (with sound insulation, ideal lighting and chroma-key background ...). before that happens, we can get a head start on capturing a few TDD best practices.

Todo

• Collect as many thoughts as we can on Testing, TDD, software reliability & maintainability.

  The objective at this stage is quantity not perfection. (we will condense and order them later!)

• Collate the thoughts into a prioritised list.
• Stitch thoughts together into a well-written post that anyone can read in 30 mins (or less)
• Publish!
• Bonus Level: Make it a PDF that people can download and read on their mobile while commuting.