[Bash-completion-commits] [SCM] bash-completion branch, master, updated. 1.3-349-ga0834d3

[Igor Murzov]

The following commit has been merged in the master branch:
commit 4f7e60a4253c46e316b9dac900249cd205f436fd
Author: Igor Murzov <e-mail at date.by>
Date:   Sat Jun 4 19:00:18 2011 +0400

    docs: Improve tester's manual

diff --git a/doc/testing.txt b/doc/testing.txt
index 62b007b..c4b7cf1 100644
--- a/doc/testing.txt
+++ b/doc/testing.txt
@@ -116,7 +116,7 @@ command has two stages which are now reflected in the two files:
 Running the tests
 -----------------
 
-The tests are run by calling `runtest` in the test directory:
+The tests are run by calling `runtest` command in the test directory:
 -----------------------
 runtest --outdir log --tool completion
 runtest --outdir log --tool install
@@ -129,6 +129,12 @@ directory:
 ./runInstall
 ./runUnit
 -----------------------
+To run a particular test, specify file name of your test as an argument to
+`runCompletion` script:
+-----------------------
+./runCompletion ssh.exp
+-----------------------
+That will run `test/completion/ssh.exp`.
 
 
 Running tests via cron
@@ -214,7 +220,13 @@ Maintenance
 Adding a completion test
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can run `cd test && ./generate` to add a test.
+You can run `cd test && ./generate cmd` to add a test for the `cmd` command.
+This will add two files with a very basic tests:
+----------------------------------
+test/completion/cmd.exp
+test/lib/completions/cmd.exp
+----------------------------------
+Place any additional tests into `test/lib/completions/cmd.exp`.
 
 
 Fixing a completion test
@@ -451,7 +463,7 @@ Within test scripts the following library functions can be used:
 
 The test environment needs to be put to fixed states when testing.  For
 instance the bash prompt (PS1) is set to the current test directory, followed
-by an ampersand (@).  The default settings for `bash` reside in `config/bashrc`
+by an at sign (@).  The default settings for `bash` reside in `config/bashrc`
 and `config/inputrc`.
 
 For each tool (completion, install, unit) a slightly different context is in

-- 
bash-completion