added run-test-suite.sh LD_LIBRARY_PATH wrapper

Makefile.am

@@ -184,6 +184,8 @@ EXTRA_DIST = \
     test/hardening-check \
     test/local_spa.key \
     test/test-fwknop.pl \
+    test/run-test-suite.sh \
+    test/README \
     VERSION \
     win32/config.h \
     win32/fwknop-client.vcproj \

test/README

@@ -0,0 +1,17 @@
+
+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

test/run-test-suite.sh

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# The safeest way to run the fwknop test suite is by using this script - on
+# some platforms setting the LD_LIBRARY_PATH variable via the standard perl
+# perl %ENV hash does not seem to work properly when running in
+# --enable-perl-module-checks mode.  This mode is used to test the perl FKO
+# libfko bindings.  CentOS 6.3 was one platform where this seemed to be an
+# issue, but setting LD_LIBRARY_PATH on the command line manually causes things
+# to work properly.
+#
+
+LD_LIBRARY_PATH=../lib/.libs ./test-fwknop.pl $@
+
+exit