Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ISC Open Source Projects
Kea
Commits
3edde39a
Commit
3edde39a
authored
Nov 06, 2012
by
Stephen Morris
Browse files
[2342] Extended documentation to discuss running of unit tests
parent
d141c47a
Changes
1
Hide whitespace changes
Inline
Side-by-side
src/lib/dhcp/database_backends.dox
View file @
3edde39a
...
...
@@ -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.
*/
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment