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

Remove some legacy test suites.

This commit is contained in:
Eric Huss 2021-11-03 17:36:35 -07:00 committed by Joshua Nelson
parent a034fad804
commit 8a8452cfcc
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/compiletest.md
View File

@ -16,9 +16,9 @@ and more. If you are unfamiliar with the compiler testing framework,
see [this chapter](./tests/intro.md) for additional background. see [this chapter](./tests/intro.md) for additional background.
The tests themselves are typically (but not always) organized into The tests themselves are typically (but not always) organized into
"suites" – for example, `run-fail`, a folder holding tests that should compile "suites" – for example, `incremental`, a folder holding tests that check
successfully, but return a failure (non-zero status) at runtime, `compile-fail`, incremental compilation behavior, `codegen`,
a folder holding tests that should fail to compile, and many more. The various a folder holding tests that check code generation, and many more. The various
suites are defined in [`src/tools/compiletest/src/common.rs`] in the suites are defined in [`src/tools/compiletest/src/common.rs`] in the
`pub enum Mode` declaration. And a good introduction to the different `pub enum Mode` declaration. And a good introduction to the different
suites of compiler tests along with details about them can be found in suites of compiler tests along with details about them can be found in

1
src/tests/adding.md
View File

@ -43,7 +43,6 @@ rough heuristics:
message is not relevant to the test. These should have an message is not relevant to the test. These should have an
[error number] (`E0XXX`) in the code block to make sure it's the correct error. [error number] (`E0XXX`) in the code block to make sure it's the correct error.
- For most other things, [a `ui` (or `ui-fulldeps`) test](#ui) is to be preferred: - For most other things, [a `ui` (or `ui-fulldeps`) test](#ui) is to be preferred:
- [`ui`](#ui) tests subsume both `run-pass`, `compile-fail`, and `parse-fail` tests
- in the case of warnings or errors, `ui` tests capture the full output, - in the case of warnings or errors, `ui` tests capture the full output,
which makes it easier to review but also helps prevent "hidden" regressions which makes it easier to review but also helps prevent "hidden" regressions
in the output in the output