acceptance test-driven development

Articles

Gold-plated leaves Build Just Enough of a Feature with ATDD

Developers have a tendency to overbuild their code. This is frequently due to not knowing exactly when they're done and not knowing how robust a feature needs to be. Acceptance test-driven development (ATDD) is a great way to avoid this practice because when the acceptance test passes, the developer knows they're done building that particular feature.

David Bernstein's picture David Bernstein
Icon showing clipboard with passed and failed tests Teaching Acceptance Test-Driven Development

Acceptance test-driven development is a whole-delivery cycle method that allows the entire team to define system behavior in specific terms before coding begins. These conversations align the expectations of the testers, developers, and product owners, forcing any silly arguments to happen before someone has to create the code twice. Here are some great beginner exercises for teaching ATDD.

Matthew Heusser's picture Matthew Heusser
From One Expert to Another: Markus Gärtner From One Expert to Another: Markus Gärtner

Markus Gärtner is a tester and the author of ATDD by Example. In this interview with Zeger van Hese, Markus talks about his new book, the software craftsmanship movement, and “Beyond Testing,” a workshop he’ll be delivering later this year.

Zeger van Hese's picture Zeger van Hese

Interviews

Agile Testing through Gaming: An Interview with Nate Oster

Nate Oster is giving two sessions at the upcoming STARCANADA 2013 that deal with empowering developers and testers through acceptance test-driven development. Oster's experience as an agile player-coach and working with test-first practices are detailed in this terrific interview.

Noel Wurst's picture Noel Wurst

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.