liveBook · Manning

Developer-only BDD

As explained in Effective Behavior-Driven Development

Developer-only BDD is a BDD practice in which developers create and apply behavior specifications without business participation.

Developer-only BDD describes teams applying BDD without business participation. Developer collaboration can provide clearer testing guidance than an ad-hoc approach, but it misses the benefits of collaboration between business stakeholders and the delivery team. section 5.2

A tool or format alone does not make an approach BDD:

  • Using BDD tools or automating Given/When/Then tests without the business is not BDD collaboration. section 5.2
  • Automated suites produced this way may be slow to run, hard to maintain, and of limited organizational value. section 5.2

How Effective Behavior-Driven Development covers it

How deep it goes
Contrasts potential testing guidance with missed collaboration benefits and test-suite drawbacks, without giving implementation steps.
Examples
Uses automated test suites and Given/When/Then tests to illustrate tool use without business involvement.
What you can do after
Evaluate whether BDD includes business collaboration rather than relying on tools or automated tests alone.
How it connects
Links BDD with business collaboration, test automation, and Given/When/Then.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.