rust/src/libcollections/Cargo.toml

[package]
authors = ["The Rust Project Developers"]
name = "collections"
version = "0.0.0"

[lib]
name = "collections"
path = "lib.rs"

[dependencies]
alloc = { path = "../liballoc" }
core = { path = "../libcore" }
rustc_unicode = { path = "../librustc_unicode" }

[[test]]
name = "collectionstest"
path = "../libcollectionstest/lib.rs"
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "collections"`
			`version = "0.0.0"`

			`[lib]`
			`name = "collections"`
			`path = "lib.rs"`

			`[dependencies]`
			`alloc = { path = "../liballoc" }`
			`core = { path = "../libcore" }`
			`rustc_unicode = { path = "../librustc_unicode" }`
rustbuild: Add support for crate tests + doctests This commit adds support to rustbuild to run crate unit tests (those defined by `#[test]`) as well as documentation tests. All tests are powered by `cargo test` under the hood. Each step requires the `libtest` library is built for that corresponding stage. Ideally the `test` crate would be a dev-dependency, but for now it's just easier to ensure that we sequence everything in the right order. Currently no filtering is implemented, so there's not actually a method of testing only libstd or only libcore, but rather entire swaths of crates are tested all at once. A few points of note here are: * The `coretest` and `collectionstest` crates are just listed as `[[test]]` entires for `cargo test` to naturally pick up. This mean that `cargo test -p core` actually runs all the tests for libcore. * Libraries that aren't tested all mention `test = false` in their `Cargo.toml` * Crates aren't currently allowed to have dev-dependencies due to rust-lang/cargo#860, but we can likely alleviate this restriction once workspaces are implemented. cc #31590 2016-04-29 16:23:15 -05:00
			`[[test]]`
			`name = "collectionstest"`
			`path = "../libcollectionstest/lib.rs"`