From: Vicky Risk Date: Thu, 15 Nov 2018 02:29:09 +0000 (-0500) Subject: Update unit-tests.dox to replace reference to oldkea.isc.org X-Git-Tag: 268-reservation-mode-is-not-global_base~28^2~13 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9d5d68034705b2244b95af5db79aadd288460533;p=thirdparty%2Fkea.git Update unit-tests.dox to replace reference to oldkea.isc.org @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 --- diff --git a/doc/devel/unit-tests.dox b/doc/devel/unit-tests.dox index 74d365cf8d..3e773686db 100644 --- a/doc/devel/unit-tests.dox +++ b/doc/devel/unit-tests.dox @@ -7,27 +7,6 @@ /** @page unitTests Building Kea with Unit Tests - -@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 @endcode Depending on how you compiled or installed \c gtest (e.g. from sources @@ -257,7 +236,7 @@ local all postgres trust The unit tests are run automatically when "make check" is executed (providing that Kea has been build with the \c --with-pgsql switch (see the installation - section in the Kea Administrator + section in the Kea Administrator Reference Manual).