Scenario Book for JiraTest results
After your tests run, your pipeline sends the report to Scenario Book with the same sync key it uses for files (see Sync with Git).
Report formats
- Cucumber JSON
- Cucumber Messages (NDJSON)
- JUnit XML
Results are matched to scenarios by feature file path, scenario name and line, then by tags. Results that match no scenario are counted and named, so you can see what didn't match.
Give a pipeline a label, such as chrome or staging, and each label keeps its own last result.
On the story
Each scenario shows its last result as a word, not a color alone: passed, failed, skipped or not run. A failed scenario says which step failed, in a sentence, with a short error. Error messages are cut to 1 KB, with terminal color codes removed.
Search with JQL
| JQL | Finds |
|---|---|
scenariosFailing > 0 | Stories with a failing scenario |
scenarioCount > 0 | Stories with at least one scenario |
scenariosNotRun > 0 | Stories with scenarios that have no result |
The story keeps counts only (scenarios, passed, failed, not run, last run), never scenario text. A story that never had a scenario has no counts, so JQL can't find it with scenarioCount = 0.
On the project page
The Results tab lists recent runs with their counts, every scenario failing in the latest run of each label with its failing step and error, a short history for each, and the results that matched no scenario.
How long results are kept
Each project keeps its last 50 test runs by default. A project admin can set any number from 1 to 1,000 in Project settings.