All courses
Frameworks · 10 lessons

BDD with Cucumber & Serenity

Turn plain-language requirements into executable specs and living documentation with the Screenplay pattern.

Beginner · 2Intermediate · 5Advanced · 3
0 of 10 lessons complete0%
Lesson 1 of 10Beginner

What is BDD?

Behaviour-Driven Development in one idea

BDD is a collaboration practice: business, development and QA agree on examples of behaviour in plain language before code is written. Those examples become automated tests — so the specification and the test are the same artifact.

The three amigos

A quick conversation between three perspectives before building a feature:

  • Business — what problem are we solving?
  • Development — how might we build it?
  • QA — what could go wrong / what are the edge cases?

The shared output is a set of concrete examples in Gherkin.

Why it helps

  • Requirements stop being ambiguous — they're executable.
  • Tests describe behaviour, not implementation, so they age well.
  • Non-technical stakeholders can read (and even help write) them.

Key takeaways

  • BDD aligns business, dev and QA on examples before coding.
  • The example is the test — spec and automation converge.
  • Gherkin is the shared language that makes it work.