-
Notifications
You must be signed in to change notification settings - Fork 21
Takes ~300ms to run 1 invocation #100
Comments
Hm, indeed. We should absolutely add this to the docs. And I'll ask the cargo team if there is a way to use cargo's "find binary" feature without having it check if it needs to compile things (which I guess is what's taking so long -- |
Another use case for such a feature is packaging. Looking into this is coming up on my plate for packaging. |
cargo issue: rust-lang/cargo#5315 |
This switches us from using `cargo run` to `cargo build`, reading where the binary is placed, and callin that instead. Fixes assert-rs#95 because the user changing the `CWD` doesn't impact `cargo build`. Fixes assert-rs#79 because there is no `cargo` output when capturing the user's stdout/stderr. Fixes assert-rs#51 because the user changing the environment doesn't impact `cargo build`. This is a step towards working around assert-rs#100 because we can allow a user to cache the result of `cargo build`.
The responsibility for this is moving to assert_cmd and tis will be addressed in assert-rs/assert_cmd#6 assert_cli is going to morph into a wider-focused tool, including things like assert_fs. See #41 |
assert_cli
version: 0.5Unfortunately,
cargo run
takes at minimum about 300ms on my computer:It makes it impractical to run hundreds of integration tests with assert_cli.
I'm not positive what a better way would be -- I guess running the binary in dist directly if it exists?
The text was updated successfully, but these errors were encountered: