3 releases (breaking)

0.4.0 Jan 26, 2022
0.3.0 Nov 26, 2019
0.2.0 Oct 6, 2019
0.1.0 Oct 5, 2019

#263 in Testing

Download history 2852/week @ 2024-06-14 2542/week @ 2024-06-21 2174/week @ 2024-06-28 1861/week @ 2024-07-05 2188/week @ 2024-07-12 2201/week @ 2024-07-19 2300/week @ 2024-07-26 2389/week @ 2024-08-02 2865/week @ 2024-08-09 2860/week @ 2024-08-16 2463/week @ 2024-08-23 2423/week @ 2024-08-30 2435/week @ 2024-09-06 2176/week @ 2024-09-13 2807/week @ 2024-09-20 2118/week @ 2024-09-27

10,135 downloads per month
Used in 11 crates

MIT/Apache

8KB

test_bin

A crate for getting the crate binary in an integration test.

If you are writing a command-line interface app then it is useful to write an integration test that uses the binary. You most likely want to launch the binary and inspect the output. This module lets you get the binary so it can be tested.

Example

Here is the basic usage:

let output = test_bin::get_test_bin("my_cli_app")
    .output()
    .expect("Failed to start my_binary");
assert_eq!(
    String::from_utf8_lossy(&output.stdout),
    "Output from my CLI app!\n"
);

Acknowledgements

The cargo and ripgrep crates were used as inspiration. They both test their binaries using a similar approach. The cargo crate's documentation and license was used as a starting point.

Contributing

See CONTRIBUTING.md.

License

The test_bin crate is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

No runtime deps