This talk is about the qualities we look for in test code that keep the development "habitable." We want to make sure the tests pull their weight by making them expressive, so that we can tell what's important when we read them and when they fail, and by making sure they don't become a maintenance drag themselves. We need to apply as much care and attention to the tests as we do to the production code, although the coding styles may differ. Difficulty in testing might imply that we need to change our test code, but often it's a hint that our design ideas are wrong and that we ought to change the production code. In practice, these qualities are all related to and support each other. Test-driven development combines testing, specification, and design into one holistic activity.

	Trust & Change Garry Shutler : 30th Jan 2012
	Continuous Delivery with Cloudbees Marco Vermeulen : 8th Dec 2011
	Building JavaScript applications Damjan Vujnovic : 29th Nov 2011
	Web architecture Uncle Bob (Robert C. Martin) : 28th Nov 2011
	Maps of Living Documentation Christian Hassa : 18th Nov 2011
	Driving Requirements from Business Value Chris Matts : 18th Nov 2011
	Visualising quality Gojko Adzic : 18th Nov 2011
	BDD As It's Meant To Be Done Matt Wynne : 18th Nov 2011
	What Testers and Developers Can Learn David Evans : 18th Nov 2011
	Where Exploration And Automation Meet: G Andrew Kemp : 18th Nov 2011
	Specifying User Interaction Lasse Koskela : 18th Nov 2011
	TDD Django Harry Percival : 16th Nov 2011
	From CI to CD : 11th Nov 2011
	To Future Branch or Not To Future B... : 11th Nov 2011
	Rolling Back Vs Rolling Forward : 11th Nov 2011