haproxy/reg-tests
Tim Duesterhus f38175cf6e MINOR: sample: Add secure_memcmp converter
secure_memcmp compares two binary strings in constant time. It's only
available when haproxy is compiled with USE_OPENSSL.
2020-06-09 22:04:13 +02:00
..
cache
checks REGTESTS: checks: Fix tls_health_checks when IPv6 addresses are used 2020-05-25 08:06:30 +02:00
compression REGTESTS: Add missing OPENSSL to REQUIRE_OPTIONS for compression/lua_validation 2020-05-26 13:36:30 +02:00
connection REGTEST: Add connection/proxy_protocol_send_unique_id_alpn 2020-05-27 13:29:56 +02:00
converter MINOR: sample: Add secure_memcmp converter 2020-06-09 22:04:13 +02:00
http-capture
http-cookies
http-errorfiles MINOR: http-htx/proxy: Add http-error directive using http return syntax 2020-05-20 18:27:14 +02:00
http-messaging MINOR: http-htx: Move htx sample fetches in the scope "internal" 2020-01-20 15:18:45 +01:00
http-rules REGTEST: http-rules: Require PCRE or PCRE2 option to run map_redirect script 2020-04-29 14:32:28 +02:00
log
lua REGTESTS: Require the version 2.2 to execute lua/set_var 2020-05-26 13:36:30 +02:00
mailers CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
mcli REGTEST: mcli/mcli_start_progs: start 2 programs 2020-01-14 15:42:38 +01:00
peers
sample_fetches MINOR: listener: add so_name sample fetch 2020-03-29 05:47:29 +02:00
seamless-reload REGTEST: increase timeouts on the seamless-reload test 2020-03-23 09:11:51 +01:00
server
spoe CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
ssl MINOR: ssl: split config and runtime variable for ssl-{min,max}-ver 2020-05-20 16:49:02 +02:00
stick-table
stickiness
stream REGTEST: make the unique-id test depend on version 2.0 2020-04-01 16:08:43 +02:00
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).