01
Select
Open a saved BDD scenario on a Jira issue and choose the coverage assessment flow.
Planning feature
Verify Jira BDD scenarios against test evidence
Let Atlassian Rovo compare a saved Jira behavior with Testream runs, explain the evidence it found, and keep reviewers in control of the final coverage decision.
Last updated August 2, 2026
Direct answer
What is BDD Coverage Agent in Testream?
Testream BDD Coverage Agent verifies whether captured automated test evidence supports a Jira BDD scenario. It compares the scenario's extracted Gherkin clauses with linked Testream evidence, then returns a coverage assessment that can be Confirmed, Likely, Not covered, Insufficient evidence, or Conflicting evidence, with confidence, rationale, provenance, and reviewer controls.
The problem
A passing test is not automatically proof that a Jira behavior is covered
Teams need to know whether the captured result matches the scenario's Gherkin clauses and expected outcome—not just whether a similarly named test passed.
What teams gain
- Compare a Jira BDD scenario with bounded candidate test details, steps, source location, and source snippets
- See confidence, rationale, matched evidence, and the provenance signals available to the assessment
- Approve or reject the assessment, then edit the scenario and reassess when it needs changes
How it works
A clear path from setup to useful evidence.
02
Assess
Rovo compares the scenario with linked runs, candidate tests, captured results, and provenance.
03
Review
Inspect the explanation, then approve or reject the assessment. Edit the scenario and reassess when it needs changes.
Product proof
Evidence-led BDD coverage review in Jira
Confirmed, Likely, Not covered, Insufficient evidence, and Conflicting evidence outcomes
Confidence, rationale, and matched evidence
Run outcome, source details, and bounded evidence provenance
Reviewer approval, rejection, and reassessment
Common questions
Questions about BDD Coverage Agent
What does the BDD Coverage Agent verify?
It assesses whether captured Testream evidence supports the extracted Gherkin clauses and expected outcome in a saved Jira BDD scenario. A passing run or similar test name is not treated as proof of full coverage by itself.
What evidence can inform a BDD coverage assessment?
The bounded Rovo assessment compares the BDD scenario with candidate evidence such as the test name, suite or framework, outcome, steps, source location, source snippet, failure summary, attachment names, and scenario or provenance signals.
Does Rovo make the final coverage decision?
No. Rovo accelerates the comparison and explains the evidence it found, while the reviewer can approve or reject the assessment. If the scenario needs changes, edit the saved scenario and start a new assessment. An unreviewed assessment should not be the only release gate.
Is BDD coverage the same as the latest test result?
No. Coverage mapping asks whether evidence appears to implement a behavior. The latest execution outcome asks whether the newest captured run passed or failed. Testream keeps those signals separate so a covered scenario can still have a failing run.
Continue exploring
Related Testream features
Planning
BDD Specs
Create, improve, and assess Gherkin acceptance criteria in Jira with reusable behavior context and real test evidence.
Platform
Rovo Setup Agent
Use the Testream Setup Agent in Jira to choose a reporter, shape CI guidance, and verify the first automated test run.
Planning
BDD Library
Create a reusable behavior library for Jira issues, test cycles, and releases without duplicating Gherkin scenarios.