Cucumber BDD (Part 1): Starting with Feature Mapping

Disclaimer: This is an extension to my previous blog article: Behavior Driven Development (BDD) & Software Testing in Agile Environments. This tutorial explains on how to apply BDD concepts and identify stories (features) in a practical Agile environment. In my next tutorial, we are gonna build a sample Java project with Cucumber, TestNG, and Maven for the better understanding of concepts studied in the first two tutorials.

Also I have implemented the steps discussed in this blog post series here: https://github.com/ashenwgt/awesome-bdd-with-cucumber. You can clone this project, modify my code, and start writing your test suite on top of it.

Origin of BDD and Cucumber

In early 2000s, there was a small clique of people from the XP community who were exploring better ways to do TDD (Test Driven Development). Dan North named this BDD (Behavior Driven Development). He is now considered as the father of BDD.

In 2008, Cucumber was created and currently it is one of the most popular BDD tools available out there. Cucumber creators (Aslak Hellesøy and team) envisioned to provide a language, a process, and a tool that would provide a single source of truth of software…