Planning feature

A lean home for manual execution and release validation

Build focused cycles from reusable behaviors, capture practical evidence, and let manual results contribute to the same release picture as automation.

Install on Jira Read the docs

Last updated July 10, 2026

Test Cycles and manual evidence in Testream — Run practical manual QA cycles from reusable BDD behaviors and connect pass, fail, blocked, and skipped outcomes to releases.

Direct answer

What is Test Cycles in Testream?

Testream Test Cycles give manual QA a lightweight Jira-native execution path. Teams assemble reusable behaviors, record outcomes and evidence, and link the cycle to a release without creating a second heavyweight test-case system.

The problem

Manual QA becomes invisible when it lives in spreadsheets and release notes

Teams need enough structure to coordinate validation without adopting duplicate test-case administration.

What teams gain

Build cycles from existing BDD Library behaviors
Record pass, fail, blocked, and skipped outcomes
Attach notes and files and link the cycle to a Jira release

How it works

A clear path from setup to useful evidence.

Assemble

Choose the behaviors that matter for this change or release.

Execute

Record an outcome, notes, and evidence for each behavior.

Surface cycle progress alongside automated evidence and release context.

Product proof

Enough structure for confidence, without heavyweight ceremony

Reusable behavior selection

Per-behavior execution status

Manual notes and evidence

Release-linked cycle progress

Continue exploring

Related Testream features

View all features

Planning

BDD Library

Create a reusable behavior library for Jira issues, test cycles, and releases without duplicating Gherkin scenarios.

Delivery

Release visibility

Review automated runs, manual cycles, behavior coverage, and evidence gaps together for clearer Jira release decisions.