BIND 10 trac2342, updated. 3edde39acb177b96c1aaa74f42562c4b7ab0488f [2342] Extended documentation to discuss running of unit tests

[BIND 10 source code commits]

The branch, trac2342 has been updated
       via  3edde39acb177b96c1aaa74f42562c4b7ab0488f (commit)
      from  d141c47a59c217c07e377a988ed92fa1cb9a3314 (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 3edde39acb177b96c1aaa74f42562c4b7ab0488f
Author: Stephen Morris <stephen at isc.org>
Date:   Tue Nov 6 14:11:17 2012 +0000

    [2342] Extended documentation to discuss running of unit tests

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

Summary of changes:
 src/lib/dhcp/database_backends.dox |   11 +++++++++++
 1 file changed, 11 insertions(+)

-----------------------------------------------------------------------
diff --git a/src/lib/dhcp/database_backends.dox b/src/lib/dhcp/database_backends.dox
index 27b4c24..7736ccb 100644
--- a/src/lib/dhcp/database_backends.dox
+++ b/src/lib/dhcp/database_backends.dox
@@ -44,4 +44,15 @@
     no password is used.
   - user - database user ID under which the database is accessed.  If not
     specified, no user ID is used - the database is assumed to be open.
+
+  @section dhcp-backend-unittest Running Unit Tests
+
+  With the use of databases requiring separate authorisation, there are
+  certain pre-requisties for scuccessfully running the unit tests.  These are
+  database-specific:
+
+  MySQL: a database called keatest needs to be set up.  A database user, also
+  called keatest (with a password keatest) must be given full privileges in
+  that database.  The unit tests create the database schema in the database
+  before each test, and delete it afterwards.
   */