test-with VS tempfile

Hi there, The 0.12 version of test-with is released. Now checking the condition to run or ignore a test is easy, we can easily set up a mock/test environment in this way. Following is an example of setting up an HTTP service in 8000 port for a test. ```rust use std::ops::Drop; use std::process::{Child, Command};

I need to do some tests with files operations, what's the best practice in regards to creating temporary files in tests ? I heard about tempfile but is there a more idiomatic way to do that ?

The sudo-rs Cargo.toml [1] file seems very reasonable. This is the curse of being cross platform. The inclusion of https://github.com/Stebalien/tempfile as a dependency is responsible for the overwhelming majority of lines due to including *-sys crates for multiple OSs.

~/Code/tempfile !! tokei vendor

Eventually, I had to test reading of input file and generation of the html file. To do this, I would need to create test files for input and output for this scenario. However, this could cause problems unless I named all the test files differently as tests usually run in parallel. So, I decided to use the tempfile crate to create a temporary test directory for each test (where needed):

Create a NamedTempFile with the tempfile crate.

Even better would be to create a tempdir and populate it during the test run. Try the tempfile crate.

Not the same commenter but you could use a tempfile

That said though; there are a few solutions for the problem you're describing. One would be to have a "temp file" type which knows how to delete itself when dropped, but can manually be converted into a permanent file in the case of success. Crates like tempfile provide abstractions for this.

tempdir was merged into tempfile.