Remove these as fuzz testing is not something that most people will do
and they are not used in ISC fuzz testing (a more extensive set of seeds
is used). In addition, it is easy enough to generate sample packets for
the fuzzer (something that is described in the developer documentation).
Indeed, with AFL, any file (not necessarily a DHCP packet) can be used
as a seed and useful results obtained.
1. Update to documentation concerning the running of until tests
which code is compiled with fuzzing enabled.
2. Correction of text of fuzzing-related initialization exception.
Two reasons:
- sphinx requires to have all sources in its source directory
so man pages have to be moved
- layout of subfolders in doc folder was not consistent
src/share/database/scripts/pgsql
wipe_data.sh.in - new file
doc/devel/unit-tests.dox
Removed MySQL/CQL only comment
several files:
Added commentary and removed superflous calls to destroyPgSQLSchema
src/lib/pgsql/testutils/pgsql_schema.*
destroyPgSQLSchema()
createPgSQLSchema() - modified to support data wiping
wipePgSQLData() - new function
src/lib/pgsql/tests
pgsql_schema.cc
pgsql_schema.h - deleted these. They appear to have
been added by mistake.
@section unitTestsIntroduction Introduction
Kea uses the Google C++ Testing Framework (also called googletest or gtest) as a
base for our C++ unit-tests. See https://github.com/google/googletest for
details. We used to have Python unit-tests inherited from BIND10
days but have been removed, so please do not write any new Kea unit
tests in Python. If you want to write DHCP tests in Python, we encourage you to
take a look at ISC Forge: http://oldkea.isc.org/wiki/IscForge .
You must have \c gtest installed or at least extracted in a directory
before compiling Kea unit-tests. To enable unit-tests in Kea, use:
@code
./configure --with-gtest=/path/to/your/gtest/dir
@endcode
or
@code
./configure --with-gtest-source=/path/to/your/gtest/dir
