diff --git a/README.md b/README.md index cbee4dd..f8cde96 100644 --- a/README.md +++ b/README.md @@ -33,6 +33,7 @@ Other crates that might be useful in testing command line programs. * [`assert_fs`][assert_fs] for filesystem fixtures and assertions. * or [tempfile][tempfile] for scratchpad directories. * [dir-diff][dir-diff] for testing file side-effects. +* [cross][cross] for cross-platform testing. [escargot]: http://docs.rs/escargot [rexpect]: https://crates.io/crates/rexpect @@ -41,6 +42,7 @@ Other crates that might be useful in testing command line programs. [duct]: https://crates.io/crates/duct [assert_fs]: https://crates.io/crates/assert_fs [commandspec]: https://crates.io/crates/commandspec +[cross]: https://github.com/cross-rs/cross ## License @@ -58,13 +60,13 @@ fitzgen > > bravo bravo WG-cli -passcod +passcod > Running commands and dealing with output can be complex in many many ways, so assert_cmd smoothing that is excellent, very much welcome, and improves ergonomics significantly. -volks73 +volks73 > I have used [assert_cmd] in other projects and I am extremely pleased with it -coreyja +coreyja > [assert_cmd] pretty much IS my testing strategy so far, though my app under test is pretty small. > > This library has made it really easy to add some test coverage to my project, even when I am just learning how to write Rust! diff --git a/src/cargo.rs b/src/cargo.rs index 71fb0fa..9669e8d 100644 --- a/src/cargo.rs +++ b/src/cargo.rs @@ -89,6 +89,12 @@ where /// /// See the [`cargo` module documentation][crate::cargo] for caveats and workarounds. /// + /// The [`Command`] created with this method may run the binary through a runner, as configured + /// in the `CARGO_TARGET__RUNNER` environment variable. This is useful for running + /// binaries that can't be launched directly, such as cross-compiled binaries. When using + /// this method with [cross](https://github.com/cross-rs/cross), no extra configuration is + /// needed. + /// /// # Examples /// /// ```rust,no_run