What is the User Story Acceptance Criteria?

A Business User Story is created to define, in a simple format, a Development request. This User Story is then used to create the success criteria for the business development request.

The success criteria defined by the business User Story becomes the blueprint for success for the Development team.  The Acceptance items are mapped to Scenarios during the Behavior Driven Development  (BDD) feature file step: Development Process Step Five.

There is a “One to One” Relationship between a Business User Story Acceptance Item and a  Behavior Driven Development Feature Scenario

The FizzBuzz User Story Acceptance Criteria Example:

As a Development Manager

I want to have an Example of the Complete Best Practice Development Process using the FizzBuzz Quiz Test

So that my Developers have a Concrete Reference for the Acceptance Test Driven Development (ATDD) and Test Driven Development (TDD) development process using Behavior Driven Development (BDD)

The FizzBuzz User Story Acceptance Criteria:

1.  Create a C# Solution called InterviewCodeQuestion using Visual Studio 2012 that contains a Console Application project assembly and a Testing assembly used to validate the Acceptance criteria below

2. Create the Collection Result of a hundred integers to for display using the FizzBuzz Quiz defined criteria 

3.  Create the Integers Results

4.  Create the Fizz Results

5.  Create the Buzz Results

6.  Create the FizzBuzz Results

7.  Display the FizzBuzz collection result in the FizzBuzz Quiz Project Console Application within the Visual Studio 2012 Solution

Steps two through six are the actual acceptance criteria for development and will map to two feature files in SpecFlow

1. FizzBuzzNumberCollectionTest.feature

2. FizzBuzzNumberTest.feature