<!-- Hi! If you want to report a bug, request a feature, or ask a question on how to use assert_cli, you have come to the right place! If you want to report a bug, please fill in the following. Otherwise, feel free to remove these lines. --> - `assert_cli` version: 0.5 - Rust version: 1.25.0 - OS and version: Ubuntu 16.04 Unfortunately, `cargo run` takes at minimum about 300ms on my computer: ``` ➜ angle-grinder git:(master) ✗ time cargo run --bin agrind -- '* | json | count' --file test_files/empty Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs Running `target/debug/agrind '* | json | count' --file test_files/empty` No data cargo run --bin agrind -- '* | json | count' --file test_files/empty 0.22s user 0.06s system 92% cpu 0.307 total ``` 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?
assert_cliversion: 0.5Unfortunately,
cargo runtakes 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?