mirror of
https://github.com/OpenVPN/openvpn.git
synced 2024-09-20 03:52:28 +02:00
5817b49b4c
In preparation to having tls-auth/crypt keys per connection block, it is important to ensure that such material is always reloaded upon SIGUSR1, no matter if `persist-key` was specified or not. This is required because when moving from one remote to the other the key may change and thus the key context needs to be refreshed. To ensure that the `persist-key` logic will still work as expected, the tls-auth/crypt key is pre-loaded so that the keyfile is not required at runtime. Trac: #720 Cc: Steffan Karger <steffan@karger.me> Signed-off-by: Antonio Quartulli <a@unstable.cc> Acked-by: Steffan Karger <steffan.karger@fox-it.com> Message-Id: <20180708024517.27108-1-a@unstable.cc> URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg17237.html Signed-off-by: Gert Doering <gert@greenie.muc.de> |
||
---|---|---|
.. | ||
example_test | ||
openvpn | ||
plugins | ||
Makefile.am | ||
README.md |
Unit Tests
This directory contains unit tests for openvpn. New features/bugfixes should be written in a test friendly way and come with corresponding tests.
Run tests
Tests are run by make check
. A failed tests stops test execution. To run all
tests regardless of errors call make -k check
.
Add new tests to existing test suite
Test suites are organized in directories. example_test/ is an example for a test suite with two test executables. Feel free to use it as a template for new tests.
Test suites
Test suites live inside a subdirectory of $ROOT/tests/unit_tests
, e.g. $ROOT/tests/unit_tests/my_feature
.
Test suites are configured by a Makefile.am
. Tests are executed by testdrivers. One testsuite can contain more than one testdriver.
Hints
- Name suites & testdrivers in a way that the name of the driver says something about which component/feature is tested
- Name the testdriver executable
*_testdriver
. This way it gets picked up by the default.gitignore
- If this is not feasible: Add all output to a
.gitignore
* Use descriptive test names:coffee_brewing__with_no_beans__fails
vs.test34
- If this is not feasible: Add all output to a
- Testing a configurable feature? Wrap test execution with a conditional (see auth_pam for an example)
- Add multiple test-drivers when one testdriver looks crowded with tests
New Test Suites
- Organize tests in folders for features.
- Add the new test directory to
SUBDIRS
inMakefile.am
- Edit
configure.ac
and add the newMakefile
toAC_CONFIG_FILES
- Run
./configure
, and enable the feature you'd like to test - Make sure that
make check
runs your tests - Check: Would a stranger be able to easily find your tests by you looking at the test output?
- Run
./configure
, and disable the feature you'd like to test - Make sure that
make check
does not run your tests