summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRobert Collins <robertc@robertcollins.net>2010-02-28 17:57:13 +1100
committerRobert Collins <robertc@robertcollins.net>2010-02-28 17:57:13 +1100
commitded100005744c74ab462543371c29e5fc9f22870 (patch)
tree8e5129b1cd3d4680b54cc58709cb93ada864ec2f /doc
parent99061e372af5b607a4f27adcc0dfe61ae694b2b8 (diff)
downloadtestrepository-ded100005744c74ab462543371c29e5fc9f22870.tar.gz
New subcommand ``run`` added which reads a .testr.conf file to figure out how
to run tests with subunit output. It then runs them and pipes into testr load. This allows simpler integration and permits a programming interface so that tools like Tribunal/Eclipe etc can refresh tests in a testrepository.
Diffstat (limited to 'doc')
-rw-r--r--doc/MANUAL.txt18
1 files changed, 17 insertions, 1 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt
index 0d45dfd..209f964 100644
--- a/doc/MANUAL.txt
+++ b/doc/MANUAL.txt
@@ -28,4 +28,20 @@ Most commands in testr have comprehensive online help, and the commands::
Will be useful to explore the system.
-
+Test Repository can be taught how to run your tests by setting up a .testr.conf
+file in your cwd. A file like::
+
+ [DEFAULT]
+ test_command=foo $IDOPTION
+ test_id_option=--bar $IDFILE
+
+will cause 'testr run' to run 'foo | testr load', and 'testr run --failing' to
+run 'foo --bar failing.list | testr load'. failing.list will be a newline separated
+list of the test ids that your test runner outputs. Having setup a .testr.conf, a
+common workflow then becomes::
+
+ # Fix currently broken tests - repeat until there are no failures.
+ $ testr run --failing
+ # Do a full run to find anything thrown out during the reduction process.
+ $ testr run
+ # And either commit or start over depending on whether errors were found.