BDD

E555967

BDD (Behavior-Driven Development) is a software development approach that emphasizes collaboration between developers, testers, and business stakeholders by defining system behavior through human-readable, example-based specifications.

All labels observed (3)

Label Occurrences
BDD canonical 2
Behavior-Driven Development 2
Specification by Example 1

How this entity was disambiguated

Statements (47)

Predicate Object
instanceOf agile software development practice ⓘ
software development methodology ⓘ
abbreviationOf Behavior-Driven Development ⓘ
appliesTo acceptance testing ⓘ
requirements analysis ⓘ
unit and integration testing ⓘ
basedOn Test-Driven Development ⓘ
belongsTo agile and lean software development family ⓘ
contrastsWith document-centric requirements approaches ⓘ
emphasizes collaboration between developers, testers, and business stakeholders ⓘ
encourages business-readable test cases ⓘ
collaborative specification workshops ⓘ
test automation at multiple levels ⓘ
focusesOn system behavior ⓘ
fullName Behavior-Driven Development ⓘ
linked to: BDD
goal align software implementation with business goals ⓘ
improve communication among project stakeholders ⓘ
reduce misunderstandings about requirements ⓘ
helpsWith bridging gap between business and technical teams ⓘ
defining clear acceptance criteria ⓘ
preventing regression through executable specs ⓘ
introducedIn mid-2000s ⓘ
keyConcept acceptance criteria ⓘ
executable specifications ⓘ
living documentation ⓘ
outside-in development ⓘ
scenarios ⓘ
ubiquitous language ⓘ
oftenImplementedWith Behave ⓘ
Cucumber ⓘ
Gherkin language ⓘ
JBehave ⓘ
SpecFlow ⓘ
linked to: Behat
originatedBy Dan North ⓘ
relatedTo ATDD ⓘ
Specification by Example ⓘ
linked to: BDD

TDD ⓘ
representsRequirementsAs concrete examples ⓘ
user-centric scenarios ⓘ
supports shared understanding of behavior ⓘ
typicalPractice derive tests from business examples ⓘ
keep specifications executable and up to date ⓘ
write scenarios before implementation ⓘ
typicalScenarioFormat Given-When-Then ⓘ
uses Given-When-Then structure ⓘ
example-based specifications ⓘ
human-readable specifications ⓘ

How these facts were elicited

Referenced by (5)

Full triples — surface form annotated when it differs from this entity's canonical label.

Sinon → relatedConcept → BDD ⓘ
TDD → relatedTo → Behavior-Driven Development ⓘ
linked to: BDD
BDD → fullName → Behavior-Driven Development ⓘ
linked to: BDD
BDD → relatedTo → Specification by Example ⓘ
linked to: BDD
Chai → supportsStyle → BDD ⓘ