Agile acceptance testing does not work, if

You forget a necessary step.

It is easy to forget a fundamental part of agile acceptance testing. It is the understanding of the story. I saw a video blog from Jeff Patton in which he mention that people tend to forget a step in user story acceptance testing. It are acceptance test! This implies you understand the story  what needs to be created. The acceptance criteria are a subset of the understanding of the story, the conformation. Which in most cases are specification by examples.

What will happen if you forget the conversation about the user story and only focus on the examples.

My personal opinion is that it maybe looking like your doing something like ATDD but it is just not right. The power is that you combine the human factor in the conversation together  with the agreement on when to accept the user story. This agreement can be perfectly captured in the examples. While exploring the specification by examples you discover new requirements that can only be successful if you understand what the goal of the user story is. Combining the acceptance testing with decent exploratory testing will get the job done.

Examples can not be the only agreement to develop a user story!


About pascaldufour

Passionate Agile Tester
This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

2 Responses to Agile acceptance testing does not work, if

  1. lisacrispin says:

    So true. We actually do a lot of exploration as we are creating executable specifications from examples. And we spend some time up front to “deep dive” with a whiteboard or mind map along with the customers and make sure we understand the purpose of the story, and explore different implementation ideas.

  2. pascaldufour says:

    This is exact why I like the definition of Craig Larman and Bas Vodde.

    A-TDD is a collaborative requirements discovery approach where examples and automatable tests are used for specifying requirements creating executable specifications

    Together with acceptance testing we are now much more focussing on visualization of the product to make the conversation and the requirements discovery more valuable. Even our test approach is now more visual.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s