Question: Silent failures blocking execution

[dimuziop]

Hi everyone,
I’ve encountered an issue that might be a bug, but I’m not entirely sure how to debug it properly since it fails silently.
Here’s a screenshot showing the debug output:

As shown in the image, the debug line prints the result yielded from the THEN step in the test:

#[then("the system should store the record temporarily in the database")]
async fn it_should_prepare_and_store_a_temporary_record(world: &mut NoCarWorld) {
    assert!(true);
    let result = world.result.as_ref().expect("Expected result");
    dbg!(result);
    assert!(result.is_ok(), "Expected operation to succeed, got: {:?}", result);
}

I’ve also tried a workaround to check for potential race conditions by adding a delay:

#[then("the system should store the record temporarily in the database")]
async fn it_should_prepare_and_store_a_temporary_record(world: &mut NoCarWorld) {
    tokio::time::sleep(std::time::Duration::from_millis(1000)).await;
    assert!(true);
    let result = world.result.as_ref().expect("Expected result");
    dbg!(result);
    assert!(result.is_ok(), "Expected operation to succeed, got: {:?}", result);
}

Here’s the result after applying the delay:

Has anyone faced a similar scenario? It seems like the assertions are never actually executed, and the test fails silently before reaching them. I’m not sure what might be causing this behavior.

TY!! Any help would be greatly appreciated—I’ve been stuck on this for the last two days! 🫠

PS: All dependencies in the service, are mocked, so there are't an actual interaction with external features.

[tyranron]

@dimuziop well, if you're using raw dbg!(), it very likely messes up with the cucumber::writer::Basic, eating parts of the output. We have this topic covered in the "Output > Terminal" chapter of the Book. As specified there, it could be more natural to use the tracing integration and use tracing::debug!() instead of dbg!().

[dimuziop]

I didn't notice that detail... Thank you so much for your help.