Crates.io | test_bin |
lib.rs | test_bin |
version | 0.4.0 |
source | src |
created_at | 2019-10-05 23:44:39.293978 |
updated_at | 2022-01-26 18:17:27.434808 |
description | A crate for getting the crate binary in an integration test. |
homepage | https://github.com/MichaelMcDonnell/test_bin |
repository | https://github.com/MichaelMcDonnell/test_bin |
max_upload_size | |
id | 170259 |
size | 20,449 |
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.
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"
);
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.
See CONTRIBUTING.md.
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.