* ``run`` now accepts ``--isolated`` as a parameter, which will cause each

  selected test to be run independently. This can be useful to both workaround
  isolation bugs and detect tests that can not be run independently.
  (Robert Collins)

1 files changed, 15 insertions, 0 deletions

diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt
index 28b286b..d0b298b 100644
--- a/doc/MANUAL.txt
+++ b/doc/MANUAL.txt
@@ -366,6 +366,21 @@ will perform that analysis for you. (This requires that your test runner is
    then either the isolation issue is racy, or it is a 3-or-more test
    isolation issue. Neither of those cases are automated today.
 
+Forcing isolation
+~~~~~~~~~~~~~~~~~
+
+Sometimes it is useful to force a separate test runner instance for each test
+executed. The ``--isolated`` flag will cause testr to execute a separate runner
+per test::
+
+  $ testr run --isolated
+
+In this mode testr first determines tests to run (either automatically listed,
+using the failing set, or a user supplied load-list), and then spawns one test
+runner per test it runs. To avoid cross-test-runner interactions concurrency
+is disabled in this mode. ``--analyze-isolation`` supercedes ``--isolated`` if
+they are both supplied.
+
 Repositories
 ~~~~~~~~~~~~