01
Capture
Save a behavior that matters beyond one ticket.
Planning feature
Turn repeated acceptance criteria into shared product knowledge
Maintain important behaviors once, then reuse them across Jira work, Test Cycles, release reviews, and evidence coverage.
Last updated July 10, 2026
Direct answer
What is BDD Library in Testream?
The Testream BDD Library keeps reusable product behaviors in one maintained catalog. Teams can link the same behavior to Jira issues, manual Test Cycles, releases, and evidence assessments instead of copying scenarios.
The problem
Copy-pasted scenarios drift away from the behavior they were meant to protect
A reusable catalog keeps language consistent and gives manual and automated evidence a stable reference point.
What teams gain
- Organize durable Gherkin behaviors
- Link behaviors to multiple Jira issues and cycles
- Preserve reviewer-owned evidence assessments
How it works
A clear path from setup to useful evidence.
02
Link
Reuse it across Jira issues, cycles, and release contexts.
03
Maintain
Improve one source as product language and evidence evolve.
Product proof
A shared behavior layer for QA, product, and engineering
Reusable Gherkin behaviors
Cross-issue linking
Cycle and release reuse
Evidence coverage history
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.
Planning
Test Cycles
Run practical manual QA cycles from reusable BDD behaviors and connect pass, fail, blocked, and skipped outcomes to releases.
Delivery
Release visibility
Review automated runs, manual cycles, behavior coverage, and evidence gaps together for clearer Jira release decisions.