I Quit BDD Once. This Time the AI Writes the Glue

Welcome to the JUG Oberpfalz Online Live Coding Sessions!
Our online sessions are held in English and streamed live on YouTube. The recording will be available afterwards. Join the live chat, ask questions, and follow along as we explore what the next generation of software development might look like.
This session is hosted by Johannes Rabauer.

**Session Topic**
On screen: a retro pixel parking garage. Cars drive in, park while their fee ticks up, and pay at the barrier on the way out. Right now the fees come from placeholder rules. By the end of the session they should come from a fee calculator built with behavior-driven development (BDD).
I tried BDD before and quit, because writing the step definitions behind every scenario was too much work. This time a person writes the scenarios in plain-language Gherkin, taken from the price list of a real parking garage, and the AI does the rest. Claude Code writes the Cucumber step definitions, runs the tests to show they fail, and implements until they pass. A hook blocks it from editing the scenarios, so it has to change the code, not the spec.
Once the tests are green, the new calculator replaces the placeholder rules and the garage starts charging the prices from the list.

**What we'll do**
* Write Gherkin scenarios for parking fees from a real price list
* Let Claude Code write the Cucumber-JVM step definitions
* Check the tests fail before any implementation exists
* Let the AI implement the fee calculator until the tests pass
* Plug the calculator into the pixel garage simulator
* Add one more rule and run the loop again
* Answer questions from the community

**Topics**
* Cucumber-JVM
* Gherkin
* JUnit 5
* Claude Code
* Spring Boot
* Behavior-driven development (BDD)
* AI coding agents
* Test automation
* Java

Whether you're a Java developer who gave up on BDD, a tester who writes acceptance criteria, or curious how far you can trust an AI with your tests, you're welcome to join.

See you in the live chat!