Scenario Book for JiraScenario Book for Jira
Write Given/When/Then scenarios on the Jira story they describe. Keep them as feature files that stay in step with your Git repository, and see on each story which scenarios passed in your last test run.
What it does
- An editor on every story: Gherkin highlighting, problems in plain words that link to their line, tables lined up with one click, step suggestions from your own project, and a version for every save.
- Feature files for the whole project: a folder tree with filters, moves and renames with a preview, and a Read tab that turns each file into living documentation.
- Two-way sync with Git, run by your own pipeline: Bitbucket Pipelines, GitHub Actions, GitLab CI, Azure Pipelines or a shell script.
- Test results on the story from your Cucumber JSON, Cucumber Messages or JUnit XML report, searchable with JQL.
- Import and export: bring in a zip of .feature files with a preview first; take the whole project out as a .zip.
Safe by design
- Never overwrites a side that changed. If Jira and Git both changed the same scenario, the story shows both versions and a person chooses.
- Edits replace exact lines. Everything else in a file stays byte for byte, so your diffs stay small.
- Runs on Atlassian. No servers of ours. Scenario Book never sends your scenarios outside Atlassian. If you turn on pipeline sync, your own pipeline downloads them into your repository, using the credentials you give it.
Price
Free for up to 10 users. Above that, priced per user through the Atlassian Marketplace, with a free trial from inside Jira.