4 releases (breaking)

0.10.0 May 23, 2023
0.9.0 May 22, 2023
0.7.0 May 21, 2023
0.6.1 May 13, 2023
0.4.5 May 13, 2023

#227 in Testing

Download history 13/week @ 2023-05-30 8/week @ 2023-06-13 16/week @ 2023-06-20 3/week @ 2023-06-27 3/week @ 2023-07-04 5/week @ 2023-07-25 1/week @ 2023-08-01 16/week @ 2023-08-08 8/week @ 2023-08-15 54/week @ 2023-08-22 16/week @ 2023-08-29 12/week @ 2023-09-05 2/week @ 2023-09-12

84 downloads per month

MIT license

350 lines


cli-sandbox is a sandboxing environment and testing utility to help you test and debug your CLI applications, inspired by Cargo's cargo-test-support.

All tests get their own temporary directories, where you can create files, check files, test your program against those files and check the output of your program in various ways.

For example, if you want to check that your Python to Rust transpiler works correctly:

use cli_sandbox::{project, WithStdout};
use std::error::Error;

fn compiling() -> Result<(), Box<dyn Error>> {
    cli_sandbox::init(); // Initialize the sandbox
    let proj = project()?;                      // Create a project

    // Let's create a file, and put in there some Python.
r#"def main():
    print("Hi! this is a test")


    let cmd = proj.command(["build"])?;         // Execute the command "<YOUR COMMAND> build". Cli-sandbox will automatically get your command.

    // Now, let's check that the transpiler created the file correctly.
r#"fn main() {
    println!("Hi! this is a test");


    // And that the command stdout and stderr are correct.

    cmd.with_stdout("File transpiled correctly! (`my-program.py` -> `my-program.rs`)");

    // If the stderr isn't empty, we'll panic.
    if !cmd.empty_stderr() {
        panic!("Something went wrong! stderr isn't empty");

You can also get the path of a project (it changes each time the tests are executed, they're temporary).


cargo add cli-sandbox --dev


The first step is to create a Project. You can use either Project::new() or project(). This will create a temporary directory for you to put all your testing files in there.

From a project, you can execute commands, do I/O operations or even operate over it manually by getting the project's path (Project::path()).

Check the project's documentation for more info.


  • Regex support for checking stdout and stderr. (feature: regex)
  • All output is beautiful thanks to pretty-assertions and better_panic. (feature: pretty, also can be enabled individually)
  • Little fuzzing functionality (feature: fuzz)
  • Testing either the debug or release profile (features: dev or release)


Check the CONTRIBUTING.md file for some guidelines on how to contribute. All contributions are welcomed, any size from contributors with all levels of experience!


we use the MIT License, check the [LICENSE] file for more information


~195K SLoC