Proper testsuite about cargo-udeps HOT 4 OPEN

4716a1e should be enough for the release.

from cargo-udeps.

How about using assert_cmd? Then we can put crates (including Cargo.lock) under tests/ as testsuites like this and run integration-tests with --target-dir ./target/tests/testapp (or $TMPDIR/cargo_udeps_tests.************/target/sampleapp).

./cargo-udeps
└── tests
    ├── testapp
    │   ├── Cargo.lock
    │   ├── Cargo.toml
    │   ├── examples
    │   │   └── example.rs
    │   ├── src
    │   │   ├── lib.rs
    │   │   └── main.rs
    │   └── tests
    │       └── test.rs
    └── testapp.rs

[package]
name = "testapp"
version = "0.0.0"
authors = ["Ryo Yamashita <[email protected]>"]
edition = "2018"
publish = false

[dependencies]
failure = "0.1.5"
structopt = "0.3.2"
termcolor = "1.0.5"

[dev-dependencies]
tempdir = "0.3.7"

[build-dependencies]
failure = "0.1.5"

from cargo-udeps.

The cargo test suite has an ability to specify Cargo.toml inline instead of having to put the Cargo.toml into a separate file. That's nicer for editing and for adding new test cases I think. We could imitate it somehow here too, maybe by creating the Cargo.toml in some temporary location (target is a good directoy for this). assert_cmd looks nice overall even though it uses lots of dependencies.

from cargo-udeps.

ability to specify Cargo.toml inline

Referring to this? I didn't know it.

from cargo-udeps.