An introduction to Behaviour Driven Development (BDD) for embedded systems
summary
Claims that BDD works for embedded systems are backed by a concrete workflow: start with example mapping to uncover rules and concrete cases, translate those into gherkin feature files, then run automation via Cucumber using a wire protocol to call step definitions on the device (cucumber-cpp listens over TCP). Recommended patterns include ports-and-adapters for decoupling and consumer-driven contracts (Pact) for hardware gaps. Cucumber is a glue runner not a magic replacement for TDD.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30Before we start
- 9:30Three practices
- 16:18Discovery
- 19:21Formulation
- 24:26Automation
- 28:18Wire protocol
- 33:04Pulling it all together
- 35:13BDD and TDD
- 36:40Agile for embedded
- 37:49Dependencies
- 38:55Decoupling
related talks
53mBehaviour Driven Development, BDD, with Cucumber for Java
45mBehaviour Driven Development: Embrace Uncertainty
16mBDD with cucumber.js
48mMake Your Life Simple and Carefree with BDD
31mBDD: Behaviour Driven Development
41mBDD Crash Course for Testers
45mLet's talk about software behaviour (BDD)
48mMake Your Life Simple and Carefree with BDD