Behavior driven development (BDD, aka Gherkin or Given-When-Then) can be an especially powerful quality aid, allowing product owners, users, testers, and developers to collaborate on how a system should act or react under various preconditions or triggers. In a UI or user-centric product, this process comes naturally to most people as they walk through the states of the user and/or product and the various steps the user takes to interact with the product and the resulting functionality. But what if there are no users? What if your product is primarily system to system interactions where users only see the outcomes indirectly, possibly through several layers of abstraction? Does BDD still apply? I believe the answer is yes. In fact, in some ways, automating test cases for system to system interactions using BDD can be simpler than user to system interactions. However, it requires a slightly different approach when crafting BDD acceptance tests for these back-end, technical integrations. Come explore these unique aspects, where you’ll gain valuable insights and practical tips for writing BDD for system to system interactions. Plus, you’ll have the opportunity to put these new skills into practice during our interactive session!