BDD

BDD evolved from TDD with the goal of addressing some of the limitations of TDD, such as test case classes filled with technical syntax that non-technical stakeholders would find difficult to read.

The concept of BDD was introduced by Dan North in 2003 during the discussions on improvement collaboration between technical and non-technical team members. This is also the year when he started the development of the JBehave framework as a replacement for the JUnit framework, emphasizing behaviors rather than tests.

The Gherkin language was created in the year after that, as a domain-specific language that is close to the natural English language. The language aims to bring non-technical stakeholders closer to technical team members.

The test scenario we have worked on during the TDD exercise can be expressed in the Gherkin language as follows:

Feature: Household creation
  Scenario: Creation of households with non-empty surnames
    Given the...