Skip to content

Update test suite descriptions. #1042

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 30, 2021
Merged

Update test suite descriptions. #1042

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions src/tests/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,17 +29,15 @@ details.
- [`ui`](./adding.html#ui) – tests that check the exact
stdout/stderr from compilation and/or running the test
- `run-pass-valgrind` – tests that ought to run with valgrind
- `run-fail` – tests that are expected to compile but then panic
during execution
- `compile-fail` – tests that are expected to fail compilation.
- `parse-fail` – tests that are expected to fail to parse
- `pretty` – tests targeting the Rust "pretty printer", which
generates valid Rust code from the AST
- `debuginfo` – tests that run in gdb or lldb and query the debug info
- `codegen` – tests that compile and then test the generated LLVM
code to make sure that the optimizations we want are taking effect.
See [LLVM docs](https://llvm.org/docs/CommandGuide/FileCheck.html) for how to
write such tests.
- `codegen-units` – tests for the [monomorphization](../backend/monomorph.md)
collector and CGU partitioning
- `assembly` – similar to `codegen` tests, but verifies assembly output
to make sure LLVM target backend can handle provided code.
- `mir-opt` – tests that check parts of the generated MIR to make
Expand All @@ -52,6 +50,9 @@ details.
ultimate in flexibility but quite annoying to write.
- `rustdoc` – tests for rustdoc, making sure that the generated files
contain the expected documentation.
- `rustfix` – tests for applying [diagnostic
suggestions](../diagnostics.md#suggestions) with the
[`rustfix`](https://github.com/rust-lang/rustfix/) crate
- `*-fulldeps` – same as above, but indicates that the test depends
on things other than `std` (and hence those things must be built)

Expand Down