Twenty years ago, I had a problem. I was working as a consultant introducing teams to ideas like continuous integration, pair-programming, and test-driven development. I was, and still am, a fan of TDD, and I was frustrated with how hard it was to get people to even try it. Most of the objections stemmed from the word ‘test’.

I tried changing my approach, using language like ‘code example’ and ‘executable spec’, and not mentioning tests at all, and that seemed to land better. People were certainly more willing to give it a try!

Fast-forward 20 years and I am amazed at the traction BDD has had. It has spawned a host of books, most of them fantastic, none of them by me. It gave rise to an ecosystem of automation tools starting in the Java and Ruby worlds as JBehave and RSpec respectively, and then exploding into the Gherkin-based tools of Cucumber, Reqnroll (née SpecFlow), and PHP’s own venerable behat.

Comments

Please login to leave a comment

Matt Raines at 11:17 on 19 Feb 2025

Good job summarising 20 years in 30 minutes.

Working in a small company I'm interested to explore whether we can take some of the Demand Led Planning ideas and apply them to improve engagement in the planning process in a single small team.

Really nice .

Great summary of the evolution of BDD

Gary Fuller at 09:50 on 20 Feb 2025

You had me at Japanese Knotweed... Really interesting talk that I hope will be applicable to our small team.