fwknop

Files

Michael Rash 2b5c38dc2b [test suite] default to not zeroing profile coverage counters

The typical work flow when generating gcov coverage results is:

- compile fwknop with coverage support
- run the test suite
- hack on fwknop
- re-run the test suite to see what coverage has been added

This work flow is much more common than collecting coverage results
for a complete test suite run. Therefore, this commit switches the
default behavior in --enable-complete mode (which enables coverage
support) to not zero-out coverage counters. A new argument
--enable-profile-coverage-init zeros the counters in preparation
for a global coverage run.

2015-06-23 16:56:25 -07:00

afl

[test suite] add fwknoprc2 file to AFL client rc test cases

2015-06-16 19:16:36 -07:00

asan

[test suite] added missing test/asan/Makefile

2015-06-18 06:16:10 -07:00

c-unit-tests

Refactored how the cunit tests are processed so "make dist" does not fail and builds with c-unit-tests enabled work on systems with firewalld (added fw_util_firewalld.c for server tests).

2015-02-14 12:29:30 -05:00

conf

[test suite] add Rijndael+HMAC test for F-Droid Fwknop2 client written by Jonathan Bennett

2015-06-16 18:32:19 -07:00

fko-wrapper

[test suite] minor Makefile update for fko-wrapper

2014-12-06 19:58:33 -05:00

fuzzing

move fuzzing_spa_packets file to perl/FKO/t/ for fuzzing tests

2013-11-26 21:44:53 -05:00

misc

[test suite] add spa_fuzzing.py and a few minor helper files for FreeBSD/OpenBSD

2014-11-01 20:44:35 -04:00

test-coverage

updated untested function list for Linux systems

2013-02-12 22:18:16 -05:00

tests

[test suite] add Rijndael+HMAC test for F-Droid Fwknop2 client written by Jonathan Bennett

2015-06-16 18:32:19 -07:00

configure_max_coverage.sh

[test suite] added configure_max_coverage.sh for --enable-complete mode

2014-05-25 16:23:40 -04:00

coverage_diff.py

[test suite] added coverage_diff.py

2014-06-01 22:30:54 -04:00

fko-python.py

[python module] default to HMAC SHA256 when an HMAC key is used but no HMAC mode was specified

2014-10-23 08:45:21 -04:00

gen-coverage-report.sh

[test suite] handle versions of lcov that don't have the --rc option

2015-03-22 17:41:26 -07:00

generate_cores.sh

[test suite] added generate_core.sh script and --enable-cores-pattern arg for the test suite

2014-10-06 21:10:02 -04:00

hardening-check

added stack protection detection for OpenBSD systems

2011-10-28 22:59:52 -04:00

init-lcov.sh

[test suite] handle versions of lcov that don't have the --rc option

2015-03-22 17:41:26 -07:00

invalid2.key

[test suite] more client/config_init.c test coverage

2014-04-07 22:31:56 -04:00

invalid3.key

[test suite] more client/config_init.c test coverage

2014-04-07 22:31:56 -04:00

invalid.args

[test suite/client] memory leak bug fix and test coverage

2014-04-08 21:12:46 -04:00

invalid.key

[test suite] more client/config_init.c test coverage

2014-04-07 22:31:56 -04:00

lcov.env

[test suite] handle versions of lcov that don't have the --rc option

2015-03-22 17:41:26 -07:00

local_spa.key

added local_spa.key file

2011-12-05 22:20:39 -05:00

long_spa.key

[test suite] add long_spa.key file

2014-03-31 13:58:40 -04:00

README

[test suite] README update to include --enable-complete mode

2014-07-22 11:31:16 -04:00

run-test-suite.sh

[test suite] buf fix for DYLD_LIBRARY_PATH on Mac OS X systems

2014-02-02 20:29:14 -05:00

spa_fuzzing.py

[test suite] SPA packet fuzzer minor comment additions to clearly define SPA packet types

2014-05-25 15:50:09 -04:00

test-fwknop.pl

[test suite] default to not zeroing profile coverage counters

2015-06-23 16:56:25 -07:00

valgrind_suppressions

[test suite] additional valgrind suppression for pcap-file processing

2014-07-03 08:52:48 -04:00

README

This directory contains the fwknop test suite.  After compiling the fwknop
sources in the parent directory of test/ the test suite can be executed.  One
of the most comprehensive ways of executing the test suite is as follows:

# ./run-test-suite.sh --enable-all

This mode enables IP resolution tests, so you will need Internet access in this
case.  If this is not possible or desirable, then another comprehensive testing
mode can be achieved with:

# ./run-test-suite.sh --enable-recompile --enable-perl-module-checks --enable-distcheck

Additional detail on the test suite (including --diff and --enable-valgrind
modes) may be found in the fwknop tutorial available here:

http://www.cipherdyne.org/fwknop/docs/fwknop-tutorial.html#3.5

For even more comprehensive testing than the --enable-all switch, you can use
--enable-complete.  However, before doing this, you will want to install the
'libfiu' fault injection library (available here: http://blitiri.com.ar/p/libfiu/),
and then compile fwknop with the 'test/configure_max_coverage.sh' script. This
provides additional arguments to the 'configure' script to build fwknop with a
maximal testing and code coverage stance. Once fwknop is compiled, then run:

# ./run-test-suite.sh --enable-complete

Note that in this mode the test suite will consume about close to 500MB of disk
space in the test/output/ directory. The main source of this data consumption
is the usage of the python SPA packet fuzzer 'test/spa_fuzzing.py'.