We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo run
Is there a reason to target the binary directly and not sit on top of cargo run?
The text was updated successfully, but these errors were encountered:
You can even target the built test binary directly with Command::new(env!("CARGO_BIN_EXE_<name>")).args([]) where <name> is the [[bin]] name.
Command::new(env!("CARGO_BIN_EXE_<name>")).args([])
<name>
[[bin]]
@mitsuhiko Probably worth to change here: https://docs.rs/insta-cmd/latest/insta_cmd/#testing-binaries
As explained here: iqlusioninc/abscissa#845
And the reason not to use something cargo run based, is also explained there.
Sorry, something went wrong.
I don't remember when this was added, or if I had just missed it, but get_cargo_bin works.
get_cargo_bin
Ah, nice! :D
No branches or pull requests
Is there a reason to target the binary directly and not sit on top of
cargo run
?The text was updated successfully, but these errors were encountered: