mirror of
https://github.com/rust-lang/cargo.git
synced 2025-09-28 11:20:36 +00:00
a49921f829
When browsing the docs, I feel like this will make it easier to tell the role of these traits within the API. Or in other words, I can easily tell that these fill a support role and for what, so I know when I care to look into them. We use this naming pattern for `cargo_test_support::paths::CargoPathExt`.
39 lines
1.4 KiB
Rust
39 lines
1.4 KiB
Rust
use cargo_test_support::compare::assert_ui;
|
|
use cargo_test_support::current_dir;
|
|
use cargo_test_support::file;
|
|
use cargo_test_support::prelude::*;
|
|
use cargo_test_support::str;
|
|
use cargo_test_support::CargoCommandExt;
|
|
use cargo_test_support::Project;
|
|
|
|
#[cargo_test]
|
|
fn case() {
|
|
cargo_test_support::registry::init();
|
|
cargo_test_support::registry::Package::new("clippy", "0.4.0+my-package").publish();
|
|
cargo_test_support::registry::Package::new("docopt", "0.6.2+my-package").publish();
|
|
cargo_test_support::registry::Package::new("regex", "0.1.1+my-package").publish();
|
|
cargo_test_support::registry::Package::new("rustc-serialize", "0.4.0+my-package").publish();
|
|
cargo_test_support::registry::Package::new("toml", "0.1.1+my-package").publish();
|
|
cargo_test_support::registry::Package::new("semver", "0.1.1")
|
|
.feature("std", &[])
|
|
.publish();
|
|
cargo_test_support::registry::Package::new("serde", "1.0.90")
|
|
.feature("std", &[])
|
|
.publish();
|
|
|
|
let project = Project::from_template(current_dir!().join("in"));
|
|
let project_root = project.root();
|
|
let cwd = &project_root;
|
|
|
|
snapbox::cmd::Command::cargo_ui()
|
|
.arg("remove")
|
|
.args(["--build", "semver"])
|
|
.current_dir(cwd)
|
|
.assert()
|
|
.success()
|
|
.stdout_eq(str![""])
|
|
.stderr_eq(file!["stderr.term.svg"]);
|
|
|
|
assert_ui().subset_matches(current_dir!().join("out"), &project_root);
|
|
}
|