BIND 10 trac1290, updated. 07520bd77da400ca476432f8bedcd934d992ec81 [1290] and some more explanation

[BIND 10 source code commits]

The branch, trac1290 has been updated
       via  07520bd77da400ca476432f8bedcd934d992ec81 (commit)
      from  2ab68057dceb0d471daf4524ba338f8f45e942f2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 07520bd77da400ca476432f8bedcd934d992ec81
Author: Jelte Jansen <jelte at isc.org>
Date:   Thu Oct 27 01:27:51 2011 +0200

    [1290] and some more explanation

-----------------------------------------------------------------------

Summary of changes:
 tests/lettuce/README |   21 ++++++++++++++++++---
 1 files changed, 18 insertions(+), 3 deletions(-)

-----------------------------------------------------------------------
diff --git a/tests/lettuce/README b/tests/lettuce/README
index 05335e6..df90ff9 100644
--- a/tests/lettuce/README
+++ b/tests/lettuce/README
@@ -30,7 +30,8 @@ The bind10 main script, bindctl script, and dig must all be in the default
 search path of your environment, and BIND 10 must not be running if you use
 the installed version when you run the tests.
 
-To run the tests, just run 'lettuce' in this directory.
+If you want to test an installed version of bind 10, just run 'lettuce' in
+this directory.
 
 We have provided a script that sets up the shell environment to run the tests
 with the build tree version of bind. If your shell uses export to set
@@ -47,8 +48,22 @@ lettuce features/<feature file>
 To run a specific scenario from a feature, use
 lettuce features/<feature file> -s <scenario number>
 
-If any scenario fails, the output from long-running processes will be stored
-in the output directory. The name of the files will be
+We have set up the tests to assume that lettuce is run from this directory,
+so even if you specify a specific feature file, you should do it from this
+directory.
+
+What to do when a test fails
+----------------------------
+
+First of all, look at the error it printed and see what step it occurred in.
+If written well, the output should explain most of what went wrong.
+
+The stacktrace that is printed is *not* of bind10, but of the testing
+framework; this helps in finding more information about what exactly the test
+tried to achieve when it failed (as well as help debug the tests themselves).
+
+Furthermore, if any scenario fails, the output from long-running processes
+will be stored in the directory output/. The name of the files will be
 <Feature name>-<Scenario name>-<Process name>.stdout and
 <Feature name>-<Scenario name>-<Process name>.stderr
 Where spaces and other non-standard characters are replaced by an underscore.