From 14717f41263c5ec9de0d8f20d2b9b458a5a1b9eb Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Mon, 26 Jun 2023 16:03:03 +0200 Subject: run-make tests: fix and improve (#1702) --- src/doc/rustc-dev-guide/src/tests/compiletest.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/doc/rustc-dev-guide') diff --git a/src/doc/rustc-dev-guide/src/tests/compiletest.md b/src/doc/rustc-dev-guide/src/tests/compiletest.md index f066992dc9d..d4730c5b490 100644 --- a/src/doc/rustc-dev-guide/src/tests/compiletest.md +++ b/src/doc/rustc-dev-guide/src/tests/compiletest.md @@ -363,7 +363,7 @@ your test, causing separate files to be generated for 32bit and 64bit systems. [`tests/mir-opt`]: https://github.com/rust-lang/rust/tree/master/tests/mir-opt -### Run-make tests +### `run-make` tests The tests in [`tests/run-make`] are general-purpose tests using Makefiles which provide the ultimate in flexibility. @@ -371,8 +371,8 @@ These should be used as a last resort. If possible, you should use one of the other test suites. If there is some minor feature missing which you need for your test, consider extending compiletest to add a header command for what you need. -However, sometimes just running a bunch of commands is really what you -need, `run-make` is here to the rescue! +However, if running a bunch of commands is really what you need, +`run-make` is here to the rescue! Each test should be in a separate directory with a `Makefile` indicating the commands to run. -- cgit 1.4.1-3-g733a5