strongswan/testing
Martin Willi b656f63efe testing: support a .gitignored testing.conf.local for site-local configurations 2013-08-29 15:55:23 +02:00
..
config Added config-3.10 2013-07-04 23:17:10 +02:00
hosts Updated PTS database scheme to new workitems model 2013-07-29 11:41:47 +02:00
images Remove executable flag from source files. 2012-05-18 10:04:08 +02:00
scripts Implemented SWID prototype IMC/IMV pair 2013-08-15 23:34:23 +02:00
tests Cleaned configuration files in PT-TLS client scenario 2013-08-22 17:24:20 +02:00
.gitignore testing: support a .gitignored testing.conf.local for site-local configurations 2013-08-29 15:55:23 +02:00
Makefile.am Removed INSTALL from EXTRA_DIST 2013-01-17 23:20:37 +01:00
README Updated documentation for the integration tests 2013-01-17 16:56:02 +01:00
do-tests testing: Ignore errors when searching for imcv log entries in daemon.log 2013-06-10 18:52:32 +02:00
make-testing Switch to 'mapped' access mode for hostfs 2013-01-17 16:55:04 +01:00
ssh Define SSHCONF from strongswan testing directory, not TESTDIR 2013-03-26 10:31:29 +01:00
ssh_config Use key(and password-)less SSH authentication 2013-01-17 15:22:09 +01:00
start-testing fix start of wpa_supplicant 2013-03-31 19:48:07 +02:00
stop-testing Make guest ACPI shutdown work 2013-01-17 16:55:03 +01:00
testing.conf testing: support a .gitignored testing.conf.local for site-local configurations 2013-08-29 15:55:23 +02:00

README

                 ------------------------------
                  strongSwan Integration Tests
                 ------------------------------


Contents
--------

   1. Building the testing environment
   2. Starting up the testing environment
   3. Running the automated tests
   4. Manual testing


1. Building the testing environment
   --------------------------------

The testing environment can be built with the "make-testing" script after
adjusting the variables in the testing.conf file.  By default everything is
built when executing the script.  Setting any of the ENABLE_BUILD_* variables
in the configuration file to "no" will not build those parts.


2. Starting up the testing environment
   -----------------------------------

When the strongSwan testing environment has been put into place by running
the "make-testing" script you are ready to start up the KVM instances by
executing the "start-testing" script.


3. Running the automated tests
   ---------------------------

The script

    ./do-tests <testnames>

runs the automated tests.  If the <testnames> argument is omitted all tests
are executed, otherwise only the tests listed will be run as shown in the
example below:

    ./do-tests ikev2/net2net-psk ikev2/net2net-cert

Each test is divided into the following phases:

    * Load the test-specific guest configuration if any is provided.

    * Next the "pretest.dat" script found in each test directory is executed.
      Among other commands, strongSwan is started on the IPsec hosts.

    * The "evaltest.dat" script evaluates if the test has been successful.

    * The "posttest.dat" script terminates the test e.g. by stopping
      strongSwan on the IPsec hosts.  It is also responsible to cleaning up
      things (e.g. firewall rules) set up in "pretest.dat".

    * Restore the default configuration on every host (new files have to be
      deleted manually in "posttest.dat").

The test results and configuration files for all tests are stored in a
folder labeled with the current date and time in the $TESTRESULTSDIR directory.

The same results are also automatically transferred to the Apache server
running on guest "winnetou" and can be accessed via the URL

    http://192.168.0.150/testresults/


4. Manual testing
   --------------

Instead of running tests automatically with "do-tests" it is possible to
preload a test scenario with the script:

    scripts/load-testconfig <testname>

Individual configuration files can be changed and any command can be executed by
logging into a guest host directly (via SSH or a console window).  No password
is required to login as root.  The sources for every software built during
"make-testing" are mounted at /root/shared/, which allows you to change and
recompile these components.

After you have finished testing, the default configuration can be restored
with the following command (newly created files have to be deleted manually)

    scripts/restore-defaults