One prelude
A public prelude exporting StepResult, Slot, ScenarioState, and the harness-context helpers, so a test imports one module.
Roadmap
Sewn, on the frame, and chalked out. Status comes from the repository’s releases and its roadmap; there are no dates here that the project has not published.
Sewn
Seven tagged releases, newest first. Each links to its notes.
Harnesses for all!
Harness adapters, with Std, Tokio, and GPUI; #[harness_context]; fallible fixtures; guard-based StepContext borrowing; a rebuild when a feature file changes; Rust 1.88.
Fully async
Async steps executed for real on Tokio’s current-thread runtime, fallible scenario bodies, and structured ExecutionError outcomes.
Tag only
A tag without published release notes.
Volkswagens
Language-server navigation from step to feature, specificity-ranked step matching, and quote-stripping string placeholders.
When I grow up
The language server’s scaffolding and on-save indexing, and the move to the stable toolchain.
Skipping and mutable fixtures
skip! and the skipped-outcome assertions, &mut fixtures in steps, cached data tables, and row-level Examples validation.
First point release
Compile-time step validation, the cargo-bdd diagnostics tool, and implicit fixture injection.
On the frame
The 0.6.1 line adds helpers, diagnostics, and tests without breaking a 0.6 suite.
A public prelude exporting StepResult, Slot, ScenarioState, and the harness-context helpers, so a test imports one module.
Compile errors that spot a non-canonical harness path or a missing attribute policy, and say how to fix it.
Tests proving the 0.6 patterns — mutable worlds, fallible fixtures, both harnesses, Outlines, skips — keep working.
Chalked out
Larger changes the roadmap records before a 1.0 release. Some may change shape before they are sewn.
Typed harness extractors for steps, configurable harness factories, one extension model for third-party harnesses, and settled async-harness semantics.
Every scenario and Outline row as its own named test with its own lifecycle and failure report.
A runtime plan that Gherkin and other front ends share, so each keeps its own source locations and the same skip and failure rules.
Hooks guaranteed to run after a scenario, whether it passed, failed, or skipped.
Parsed Gherkin cached in OUT_DIR, so large suites do not parse the same files on every build.
A rust-analyzer procedural-macro server or a VS Code extension, and skipped scenarios surfaced in the editor.