diff options
| author | Robert Collins <robertc@robertcollins.net> | 2012-12-06 13:39:10 +1300 |
|---|---|---|
| committer | Robert Collins <robertc@robertcollins.net> | 2012-12-06 13:39:10 +1300 |
| commit | e4b03f60a2b8b9b1a4d14c635e0b21799f6779d0 (patch) | |
| tree | f06e6fb43b5aad02797be63f5268d4b9a3f76d40 /doc | |
| parent | 04ffb4317040c0beb4f473519c4a5f70263a144e (diff) | |
| download | testrepository-git-e4b03f60a2b8b9b1a4d14c635e0b21799f6779d0.tar.gz | |
More accurate getting-going docs.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/MANUAL.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt index 7a7b327..fafd16e 100644 --- a/doc/MANUAL.txt +++ b/doc/MANUAL.txt @@ -11,6 +11,8 @@ Typical workflow is to have a repository into which test runs are inserted, and then to query the repository to find out about issues that need addressing. For instance, using the sample subunit stream included with Test repository:: + # Note that there is a .testr.conf already: + ls .testr.conf # Create a store to manage test results in. $ testr init # add a test result (shows failures) @@ -23,6 +25,7 @@ instance, using the sample subunit stream included with Test repository:: $ testr failing Most commands in testr have comprehensive online help, and the commands:: + $ testr help $ testr commands @@ -31,7 +34,7 @@ Will be useful to explore the system. Running tests ~~~~~~~~~~~~~ -Test Repository can be taught how to run your tests by setting up a .testr.conf +testr can be taught how to run your tests by setting up a .testr.conf file in your cwd. A file like:: [DEFAULT] |