mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention running tests for subdirectories

This commit is contained in:
varkor 2019-05-15 08:58:20 +01:00 committed by Who? Me?!
parent d67561391a
commit c2c7085f77
2 changed files with 22 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/how-to-build-and-run.md
View File

@ -297,6 +297,10 @@ in other sections:
more details): more details):
- `./x.py test --stage 1 src/libstd` – runs the `#[test]` tests from libstd - `./x.py test --stage 1 src/libstd` – runs the `#[test]` tests from libstd
- `./x.py test --stage 1 src/test/run-pass` – runs the `run-pass` test suite - `./x.py test --stage 1 src/test/run-pass` – runs the `run-pass` test suite
- `./x.py test --stage 1 src/test/ui/const-generics` - runs all the tests in
the `const-generics/` subdirectory of the `ui` test suite
- `./x.py test --stage 1 src/test/ui/const-generics/const-types.rs` - runs
the single test `const-types.rs` from the `ui` test suite
### ctags ### ctags

21
src/tests/running.md
View File

@ -47,6 +47,19 @@ the debuginfo test suite:
> ./x.py test --stage 1 src/test/debuginfo > ./x.py test --stage 1 src/test/debuginfo
``` ```
If you only need to test a specific subdirectory of tests for any
given test suite, you can pass that directory to `x.py test`:
```bash
> ./x.py test --stage 1 src/test/ui/const-generics
```
Likewise, you can test a single file by passing its path:
```bash
> ./x.py test --stage 1 src/test/ui/const-generics/const-test.rs
```
### Run only the tidy script ### Run only the tidy script
```bash ```bash
@ -82,8 +95,9 @@ work well with procedural macros or custom derive tests.
## Running an individual test ## Running an individual test
Another common thing that people want to do is to run an **individual Another common thing that people want to do is to run an **individual
test**, often the test they are trying to fix. One way to do this is test**, often the test they are trying to fix. As mentioned earlier,
to invoke `x.py` with the `--test-args` option: you may pass the full file path to achieve this, or alternatively one
may invoke `x.py` with the `--test-args` option:
```bash ```bash
> ./x.py test --stage 1 src/test/ui --test-args issue-1234 > ./x.py test --stage 1 src/test/ui --test-args issue-1234
@ -91,7 +105,8 @@ to invoke `x.py` with the `--test-args` option:
Under the hood, the test runner invokes the standard rust test runner Under the hood, the test runner invokes the standard rust test runner
(the same one you get with `#[test]`), so this command would wind up (the same one you get with `#[test]`), so this command would wind up
filtering for tests that include "issue-1234" in the name. filtering for tests that include "issue-1234" in the name. (Thus
`--test-args` is a good way to run a collection of related tests.)
## Using incremental compilation ## Using incremental compilation