diff options
| author | bors <bors@rust-lang.org> | 2016-05-12 14:31:54 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2016-05-12 14:31:54 -0700 |
| commit | 4ec5ce5e44823c29d4f641f764e53d57e8b28a6a (patch) | |
| tree | 140b6c4e9f7a05a813227174e754d3f92dee74fd /src/liballoc_system | |
| parent | e88defe71806ad190588e168e513bc1098f7c9fb (diff) | |
| parent | bb9062a2967a5b772788aa14f742d8927ac040ba (diff) | |
| download | rust-4ec5ce5e44823c29d4f641f764e53d57e8b28a6a.tar.gz rust-4ec5ce5e44823c29d4f641f764e53d57e8b28a6a.zip | |
Auto merge of #33282 - alexcrichton:rustbuild-crate-tests, r=brson
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
Diffstat (limited to 'src/liballoc_system')
0 files changed, 0 insertions, 0 deletions
