haproxy/reg-tests
Jarno Huuskonen 1261a87df9 DOC: REGTESTS README varnishtest -Dno-htx= define.
Add -Dno-htx= to varnishtest command line, because without no-htx most
vtc tests fail (${no-htx} macro). Also link to doc/regression-testing.txt
2019-01-14 10:52:28 +01:00
..
cache REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
checks REGTEST: Add a reg test for health-checks over SSL/TLS. 2019-01-08 10:10:18 +01:00
compression REGTEST: filters: add compression test 2019-01-09 14:36:22 +01:00
connection REGTEST: Missing enclosing quotes for ${tmpdir} macro. 2018-12-20 11:00:17 +01:00
http-capture REGTEST: "capture (request|response)" regtest. 2019-01-09 10:06:10 +01:00
http-cookies REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
http-messaging REGTESTS: remove the expected window updates from H2 handshakes 2018-12-23 09:58:41 +01:00
http-rules REGTESTS: Basic tests for using maps to redirect requests / select backend 2019-01-14 10:52:28 +01:00
log REGTEST/MINOR: remove health-check that can make the test fail 2018-12-09 00:11:09 +01:00
lua REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
mailers REGTEST: mailers: add new test for 'mailers' section 2019-01-08 10:03:52 +01:00
seamless-reload REGTEST: Missing enclosing quotes for ${tmpdir} macro. 2018-12-20 11:00:17 +01:00
server REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
spoe REGTEST/MINOR: Add a new class of regression testing files. 2018-08-23 15:47:10 +02:00
ssl REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
stick-table REGTEST: Add option to use HTX prefixed by the macro 'no-htx' 2018-12-20 10:37:32 +01:00
README DOC: REGTESTS README varnishtest -Dno-htx= define. 2019-01-14 10:52:28 +01:00

README

                 * Regression testing for HAProxy with varnishtest *


This little README file is about how to compile and run varnishtest test case files (VTC files) to test HAProxy for any regression.

To do so, you will have to compile varnishtest program sources which comes with
Varnish cache application. varnishtest is a very useful program which has been
developed to test Varnish cache application. varnishtest has been modified in
collaboration with Varnish cache conceptor Poul-Henning Kamp to support HAProxy in
addition to Varnish cache.
See also: doc/regression-testing.txt

* varnishtest compilation *

  - Clone recent Varnish cache sources which may be found in this GitHub repository
    https://github.com/varnishcache/varnish-cache:

    $ git clone https://github.com/varnishcache/varnish-cache

  - Compile Varnish cache sources:

    $ cd varnish-cache && ./autogen.sh && ./configure && make

  Then varnishtest program may be found in bin/varnishtest directory.
  VTC files for Varnish cache may be found in bin/varnishtest/tests directory.
  The Varnish cache manuals are located in 'man' directory. You will have to
  have a look at varnishtest(7) and vtc(7) manuals.

  Some information may also be found in doc/regression-testing.txt in HAProxy
  sources.


* varnishtest execution *

  You must set HAPROXY_PROGRAM environment variable to give the location
  of the HAProxy program to test to varnishtest:

    $ HAPROXY_PROGRAM=<my haproxy program> varnishtest [-Dno-htx=] ...

  The HAProxy VTC files found in HAProxy sources may be run with the reg-tests
  Makefile target. You must set the VARNISHTEST_PROGRAM environment variable to
  give the location of the varnishtest program which has been previously compiled.

    $ VARNISHTEST_PROGRAM=<my varnishtest program> HAPROXY_PROGRAM=<my haproxy program> make reg-tests

  Note that varnishtest is run with -t5 and -l option. -l option is to keep
  keep varnishtest temporary directory in case of failed test cases. core files
  may be found in this directory (if enabled by ulimit).


* varnishtest patches for HAProxy VTC files *

  When producing a patch to add a VCT regression testing file to reg-tests directory,
  please follow these simple rules:

    - Add the commit number on the first line.
    - Then, copy and paste the commit log.
    - If your VTC file needs others files, use the same basename as that of the VTC
      file.
    - Put these files in a directory with the same name as the code area concerned
      by the bug ('peers', 'lua', 'acl' etc).