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 […]
Major update to AssertThat BDD Cucumber for Jira Cloud featuring migration to Atlassian Forge, improved automation reporting, enhanced issue view testing and AI scenario generation coming next month.
Behaviour-Driven Development (BDD) and Cucumber have become essential practices for teams wanting clearer requirements, improved collaboration, and reliable automated testing. But when organisations scale BDD inside Jira, teams face common questions about writing Gherkin, integrating automation frameworks, synchronising feature files with Git, managing test results, and combining manual and automated scenario execution. To help development,
For many teams working in Jira, the early stages of test design remain a significant constraint. Requirements may move quickly through refinement and development—often accelerated further by AI—but translating them into structured, high-quality test cases is still labour-intensive. Testers often repeat similar patterns of work or compensate for inconsistencies across contributors. The result is predictable:
We have outlined our roadmap to provide visibility of the next set of exciting features for the plugin. The features and enhancements are based on feedback and conversations we have had with our customers. If you would like to see a new feature or enhancement to the plugin then please get in contact at [email protected]
