rstest‑bdd seeks to bring the collaborative clarity of Behaviour‑Driven
Development to Rust without sacrificing the ergonomics of rstest and the
convenience of cargo test. In its present form, the framework provides a core
workflow: write Gherkin scenarios, implement matching Rust functions with
#[given], #[when] and #[then] annotations, rely on matching parameter
names for fixture injection (use #[from] when renaming), and bind tests to
scenarios with #[scenario]. Step definitions are discovered at link time via
the inventory crate, and scenarios execute all steps in sequence before
running any remaining test code. While advanced Gherkin constructs and
parameterization remain on the horizon, this foundation allows teams to
integrate acceptance criteria into their Rust test suites and to engage all
three amigos in the specification process.