Writing BDD scenarios takes time. Anyone who has sat down to convert a backlog of user stories into well-structured Gherkin test cases knows the drill — it’s important work, but it’s also repetitive, and it pulls QA engineers away from the higher-value thinking that actually improves test coverage. We’ve been thinking about this problem for […]
AI test case generation Jira is demonstrated in this walkthrough, showing how to generate test cases using your own LLM and import them directly into Xray using VibeTester. In this video, we cover how to configure OpenAI (or other supported LLM providers) within VibeTester, set up the Xray test management integration, and enable the app
Refinement is the part of BDD that most teams underestimate. Scenarios are written with good intent, validated, and then quietly left alone while the product continues to change. Over time, behaviour drifts, wording becomes inconsistent, and scenarios no longer reflect how the system actually works. This doesn’t usually happen because teams stop caring. It happens
Validation is where Behaviour-Driven Development either earns trust or quietly loses it. Teams can spend time agreeing behaviour and writing clear scenarios, but without visible validation those scenarios don’t carry much weight. If people can’t see what has actually run — and what the outcome was — BDD starts to feel theoretical rather than reliable.
BDD automation is often where expectations and reality start to drift apart. Teams talk about “automating BDD” as if it is the goal in itself. In practice, automation is just one part of the picture. It’s useful only if it reinforces the behaviour that was agreed earlier — not if it quietly replaces it. Automation
