01
Describe
Capture the behavior a Jira issue must deliver in readable Gherkin.
Planning feature
Make acceptance criteria specific, reusable, and assessable
Write Gherkin where delivery work happens, reuse shared behaviors, and connect each scenario to the evidence that proves it works.
Last updated July 10, 2026
Direct answer
What is BDD Specs in Testream?
Testream BDD Specs add a practical Gherkin layer to Jira issues. Teams can draft and improve scenarios with Atlassian Rovo, connect reusable behaviors, and review how captured evidence supports each behavior while keeping the BDD Spec as the source of truth.
The problem
Acceptance criteria lose value when they cannot be reused or checked
Scenarios copied across issue descriptions drift quickly and rarely stay connected to the tests that validate them.
What teams gain
- Draft or refine Gherkin with Rovo in Jira
- Reuse BDD Library behaviors across issues
- Review confirmed, likely, or not-covered evidence assessments
How it works
A clear path from setup to useful evidence.
02
Reuse
Link established behaviors instead of duplicating shared scenarios.
03
Assess
Compare captured test evidence with the expected behavior and keep reviewer control.
Product proof
BDD that connects product intent to delivery evidence
Issue-level Gherkin specifications
Rovo-assisted drafting
Reusable library behaviors
Reviewer-controlled evidence assessment
Continue exploring
Related Testream features
Planning
BDD Library
Create a reusable behavior library for Jira issues, test cycles, and releases without duplicating Gherkin scenarios.
Planning
BDD Coverage Agent
Use Atlassian Rovo to assess BDD scenarios against captured Testream evidence with confidence, rationale, and reviewer control.
Planning
Test Cycles
Run practical manual QA cycles from reusable BDD behaviors and connect pass, fail, blocked, and skipped outcomes to releases.