Acceptance Test Driven Development is a very popular topic these days. Everybody’s excited about the idea of writing tests prior to development.
And yet many teams run into difficulties as they attempt to implement this practice. It is all too easy to fall into the trap of writing acceptance tests that specify every keystroke and button click. Acceptance tests that are tightly coupled to the system under tests are the norm. Most software changes over time and our tests need to be able to adapt to that change.
Join Cheezy as he shares the experience and insight he has gained while working with numerous teams implementing ATDD. Cheezy takes us on a journey of discovery where he demonstrates techniques to write Acceptance Tests that describe the essence of what they are specifying while hiding unnecessary details that obfuscate their meaning. Cheezy also demonstrates how to structure and layer your test code to reduce brittleness and fragility so it will retains its usefulness well into the future.
