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.
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 NERFINISHED ⓘ |
| 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
NERFINISHED
ⓘ
Cucumber NERFINISHED ⓘ Gherkin language NERFINISHED ⓘ JBehave NERFINISHED ⓘ SpecFlow NERFINISHED ⓘ |
| originatedBy | Dan North NERFINISHED ⓘ |
| relatedTo |
ATDD
ⓘ
Specification by Example NERFINISHED ⓘ 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 ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.