Behavior-Driven Development - CI/CD Glossary Definition
Behavior-driven development expresses tests as readable behavior scenarios shared across the whole team.
Behavior-driven development (BDD) extends TDD by describing desired behavior in natural language (Given, When, Then) that both business and engineering can read, then automating those scenarios as tests.
BDD, associated with Dan North, shifts the focus from testing implementation to specifying behavior. Frameworks like Cucumber and SpecFlow execute the scenarios.
In CI
BDD scenario suites run in the pipeline like any other tests, providing both regression protection and human-readable documentation.
Related guides
Given, When, Then - CI/CD Glossary DefinitionGiven, When, Then: Given, When, Then is a template for expressing a test or scenario in plain language: given…
Test-Driven Development - CI/CD Glossary DefinitionTest-Driven Development: Test-driven development (TDD) is a practice of writing a failing test before writing…
Acceptance Test-Driven Development - CI/CD Glossary DefinitionAcceptance Test-Driven Development: Acceptance test-driven development (ATDD) is a collaborative practice whe…