haproxy/reg-tests
Thayne McCombs 23cc52d34b REGTESTS: add test for stickiness using "srvkey addr"
This tests the new "srvkey addr" stick-table statement, which sticks based
on the server's address.
2020-12-31 10:08:54 +01:00
..
balance REGTEST: fix host part in balance-uri-path-only.vtc 2020-09-29 10:52:27 +02:00
cache BUG/MEDIUM: cache: Fix hash collision in accept-encoding handling for Vary 2020-12-31 09:39:08 +01:00
checks REGTESTS: complete http-check test 2020-12-22 14:22:44 +01:00
compression
connection REGTESTS: Fix proxy_protocol_tlv_validation 2020-12-04 14:41:49 +01:00
converter REGTESTS: converter: add url_dec test 2020-11-17 11:53:25 +01:00
filters REGTESTS: Add a script to test the random forwarding with several filters 2020-11-17 11:34:36 +01:00
http-capture
http-cookies MEDIUM: proxy: remove start_proxies() 2020-10-09 11:27:30 +02:00
http-errorfiles
http-messaging
http-rules MINOR: http_act: Add -m flag for del-header name matching method 2020-11-21 15:54:30 +01:00
http-set-timeout REGTESTS: add regtest for http-request set-timeout 2020-12-11 12:01:07 +01:00
log CLEANUP: assorted typo fixes in the code and comments 2020-12-21 11:24:48 +01:00
lua REGTESTS: add a test for the threaded Lua code 2020-12-02 21:53:16 +01:00
mailers
mcli
peers
sample_fetches REGTESTS: add tests for the xxh3 converter 2020-12-23 06:39:21 +01:00
seamless-reload REGTESTS: mark the abns test as broken again 2020-11-17 11:45:10 +01:00
server REGTEST: server/cli_set_ssl.vtc requires OpenSSL 2020-11-18 17:41:28 +01:00
spoe
ssl CLEANUP: assorted typo fixes in the code and comments 2020-12-21 11:24:48 +01:00
stick-table REGTEST: remove stray leading spaces in converteers_ref_cnt_never_dec.vtc 2020-08-19 11:20:28 +02:00
stickiness REGTESTS: add test for stickiness using "srvkey addr" 2020-12-31 10:08:54 +01:00
stream
webstats
README

                 * Regression testing for HAProxy with VTest *


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

To do so, you will have to compile vtest program sources which depends on
Varnish cache application sources. vtest, formerly varnishtest, is a very useful
program which has been developed to test Varnish cache application. vtest 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

* vtest compilation *

    $ git clone https://github.com/vtest/VTest

    $ cd VTest

    $ make vtest

  Then vtest program may be found at the root directory of vtest sources directory.
  The Varnish cache manuals are located in 'man' directory of Varnish cache sources
  directory. You will have to have a look at varnishtest(7) and vtc(7) manuals to
  use vtest.

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

  Note that VTC files for Varnish cache may be found in bin/varnishtest/tests directory
  of Varnish cache sources directory which may be found here:
  https://github.com/varnishcache/varnish-cache


* vtest execution *

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

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

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

    $ VTEST_PROGRAM=<my vtest program> make reg-tests

  "reg-tests" Makefile target run scripts/run-regtest.sh script.
  To get more information about this script run it with --help option.

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


* vtest patches for HAProxy VTC files *

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

    - If your VTC file needs others files, if possible, 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).