ATDD SpecFlow Feature File
What is the ATDD SpecFlow Feature File?
The challenge that the Modern Develop has with User Story Acceptance Criteria is how to put “Teeth” into a paper requirement. Behavior Driven Development (BDD) gives us a mechanism to do just that.
Using a tool like SpecFlow we can define Development Scenarios that map one to one to the User Story Acceptance Criteria.
Feature file scenarios define the highest level of abstraction integration tests that map to the acceptance criteria defined in the User Story
SpecFlow uses a special language called Gherkin to create the test code scaffolding. This is actual code that is put in the Testing Assembly.
The code is run to create Website pages for all Agile Team Members to view. The Business Stakeholders can validate the Development Road Map that these code scenarios create for the Developers.
Here is an Example of a SpecFlow Feature File:
Here is a User Story Mapped to the Feature File:
By right mouse clicking anywhere within the SpecFlow Feature file text a context menu will give you the ability to copy the generated Gherkin code to the clipboard.
Paste the Generated Gherkin Code in the SpecFlow Steps File Scaffolding that will be Created for You in the Next Step
This will generate the YELLOW Inconclusive ATDD status and will be posted to a Website that all can view. This is the first stage of ATDD Acceptance Tests.
The following two tabs change content below.
I am a Principal Architect at Liquid Hub in the Philadelphia area specializing in Agile Practices as a Certified Scrum Master (CSM). I use Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) with Behavior Driven Development (BDD) as my bridge to Agile User Stories Acceptance Criteria in a Domain Driven Design (DDD) implementing true RESTful services
Latest posts by Brad Huett (see all)
- DevOps: A Bridge to Your DevOps Culture - March 25, 2016
- Embracing Test Driven Development (TDD) - March 25, 2016
- DevOps: Delivering Agile Projects - March 25, 2016