BDD with cucumber.js
summary
Describes using cucumber.js to connect concrete feature file examples (a 30‑year fixed mortgage) to step definitions so natural language becomes executable tests, explaining the AST, ambiguous‑step and missing‑step errors and why some teams duplicate checks in two places. Argues BDD is about managing complexity via Given When Then (state → action → outcome), compares tool scale (GCC ~14.5M LOC, create‑react‑app ~1,070,841 LOC) and offers a two‑day BDD kickstart class.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:16BDD WITH CUCUMBER
- 1:07TEAM COLLABORATES NATURAL LANGUAGE DESCRIPTION CONNECT TO AUTOMATED TESTS LIVING DOCUMENTATION
- 8:29COMPLEXITY & COMMUNICATION
related talks
36mBDD With Cucumber
50mMake BDD great again
26mNot your unit test
44mBDD with JUnit 5 and Cucumber
08m"BDD: NOT The Given-When-Then Thing"
53mBehaviour Driven Development, BDD, with Cucumber for Java
50mAn introduction to Behaviour Driven Development (BDD) for embedded systems
45mLet's talk about software behaviour (BDD)