Fighting against technical debt with BDD, DevOps and Sustainability
summary
Claim: BDD alone is not enough. Example projects use a cucumber-to-.NET stack with BDD scenarios (about few hundred scenarios) that protect the external contract while the internals get a huge architecture overhaul — a refactor reverses decisions and succeeds because scenarios preserve business behaviour. Another project pairs BDD with monitoring and a fast release pipeline so operational faults are fixed live. A third project misuses BDD and ends with tests run seven hours, killing rapid feedback and sustainability.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:15Illusions
- 1:50Not perfect
- 3:15Testing is a solution
- 3:55Three quality aspects
- 5:00Reversibility
- 5:50Delaying decisions
- 7:20BDD
- 7:45Ice Cream
- 8:10Hard Shell Container
- 10:40BDD scenarios
- 13:25Was it a success
- 14:25DevOps
- 16:35Sustainability
- 17:00Hoover story
- 19:15Success and sustainability
- 19:25The third project
- 21:00Summary
- 22:25Backend related scenarios
related talks
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
09m"Effective ways of using BDD concept for Testing"
48mBDD - It’s More Than Acceptance Tests
51mDoes BDD Adds Additional Architectural Limitations on Solutions for Testing?
08m"BDD: NOT The Given-When-Then Thing"
20mBDD: You’re doing it wrong!
40mMaking BDD Work for you
26mNot your unit test