You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there may be a bug with --fail-fast behavior. I'm assuming it should force cucumber to exit on first failure. Instead I'm seeing step failure (as expected) and afterwards it just hangs (doesn't exit, seems to be stuck in an infinite loop somewhere).
# tests/scenarios
use cucumber::{then,World as _};#[derive(cucumber::World,Debug,Default)]structWorld;#[then(expr = "step panics")]asyncfnstep_panics(_:&mutWorld){panic!("this is a panic message");}#[then(expr = "nothing happens")]asyncfnnothing_happens(_:&mutWorld){// noop}#[tokio::main]asyncfnmain(){World::cucumber().max_concurrent_scenarios(1).run_and_exit("tests/check.feature").await;}
I think there may be a bug with
--fail-fast
behavior. I'm assuming it should force cucumber to exit on first failure. Instead I'm seeing step failure (as expected) and afterwards it just hangs (doesn't exit, seems to be stuck in an infinite loop somewhere).Cargo.toml:
And run like this:
cargo test --test scenarios -- --fail-fast
The text was updated successfully, but these errors were encountered: