-
Notifications
You must be signed in to change notification settings - Fork 549
Closed
Labels
E-easyDifficulty: might be a good place for a beginnerDifficulty: might be a good place for a beginner
Description
This section should describe how to compiler is tested. Substantial work has been done but there remains more to document:
- discuss bors, travis, platform emulation (Start documentation for test infrastructure. #66 )
- crater: what is it and why is it useful? How do you request a crater run and when should you to do so? (Add a bit about crater #151)
- maybe talk about "perf runs" too (Add a bit about crater #151)
- rustdoc tests (cc @QuietMisdreavus)
- talk about unit tests from libs and things (Add some more information about the various tests that get run. #62)
- Doctests: How to run the doc tests in the standard library. Other doc testing steps like linkchecker. (Add some more information about the various tests that get run. #62)
- distcheck (Add some more information about the various tests that get run. #62)
- mention that tests also get run for individual packages, such as bootstrap, cargo, rls, rustfmt, miri, clippy, cargotest. (Add some more information about the various tests that get run. #62)
Metadata
Metadata
Assignees
Labels
E-easyDifficulty: might be a good place for a beginnerDifficulty: might be a good place for a beginner