Tag Archive: ATDD

Executable Specifications

October 29, 2013

How do we specify requirements? Chatting is inherently imprecise. Email looses context. Even the ideal requirement document starts to decay once it is done. The most precise way we know to store knowledge is code. Could we use code to write specifications that are easy to understand by non-technical stakeholders and that check the behavior... Read more

Markus Gärtner talking about Acceptance Test Driven Development (ATDD)

October 15, 2013

Like the “Test Driven Development (TDD)” which involves automated small unit tests guiding corresponding implementation, the “Acceptance Test Driven Development (ATDD)” means to create tests before code, showing the behaviour that the software should have and the stakeholders want. Markus Gärtner is talking about his workshop “Acceptance Test Driven Development”. Check out his talk: Would you... Read more