From 5f32a38a3d083256f917342717bbca008cd0deff Mon Sep 17 00:00:00 2001 From: clubby789 Date: Sat, 28 Dec 2024 11:55:20 +0000 Subject: [PATCH] Document `x test --no-capture` (#2174) --- src/tests/compiletest.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/tests/compiletest.md b/src/tests/compiletest.md index 815509a82..17106be46 100644 --- a/src/tests/compiletest.md +++ b/src/tests/compiletest.md @@ -33,6 +33,14 @@ See the [Adding new tests](adding.md) and [Best practies](best-practices.md) chapters for a tutorial on creating a new test and advice on writing a good test, and the [Running tests](running.md) chapter on how to run the test suite. +Arguments can be passed to compiletest using `--test-args` or by placing them after `--`, e.g. +- `x test --test-args --force-rerun` +- `x test -- --force-rerun` + +Additionally, bootstrap accepts several common arguments directly, e.g. + +`x test --no-capture --force-rerun --run --pass`. + Compiletest itself tries to avoid running tests when the artifacts that are involved (mainly the compiler) haven't changed. You can use `x test --test-args --force-rerun` to rerun a test even when none of the inputs have changed.