haproxy/reg-tests
Willy Tarreau dce394a303 REGTESTS: silence warnings about content-type being ignored
The following rules are triggering warnings about content-type being
ignored:

  http-request return content-type "text/plain" if { path /def-4 }
  http-request return content-type "text/plain" file /dev/null hdr "x-custom-hdr" "%[url]"  if { path /empty-file }

Annoyingly, the content-type is mandatory when the file is not empty,
that might be something to revisit in the future to relax at least one
of the rules so that the config doesn't strictly require to know the
file contents upfront.
2024-11-19 08:06:26 +01:00
..
balance
cache REGTESTS: cache: Add test on 'vary' other than accept-encoding 2024-04-29 10:41:48 +02:00
checks REGTESTS: make the unit explicit for very short timeouts 2024-11-19 08:06:26 +01:00
compression REGTESTS: silence the "log format ignored" warnings 2024-11-19 08:06:26 +01:00
connection REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
contrib
converter REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
filters
http-capture
http-cookies
http-errorfiles REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
http-messaging REGTESTS: Never reuse server connection in http-messaging/truncated.vtc 2024-10-17 14:44:01 +02:00
http-rules REGTESTS: silence warnings about content-type being ignored 2024-11-19 08:06:26 +01:00
http-set-timeout
jwt
log REGTESTS: make the unit explicit for very short timeouts 2024-11-19 08:06:26 +01:00
lua REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
mailers
mcli REGTESTS: cli: add delay 0.1 before connect to cli 2024-10-16 22:00:58 +02:00
peers
pki
sample_fetches REGTESTS: silence warnings about content-type being ignored 2024-11-19 08:06:26 +01:00
seamless-reload REGTESTS: silence the "log format ignored" warnings 2024-11-19 08:06:26 +01:00
server REGTESTS: silence the "log format ignored" warnings 2024-11-19 08:06:26 +01:00
spoe MAJOR: spoe: Let the SPOE back into the game 2024-05-22 09:04:38 +02:00
ssl REGTESTS: ssl: test the issuers-chain-path keyword 2024-07-17 16:52:06 +02:00
startup
stats REGTESTS: replace REQUIRE_VERSION by version_atleast 2024-05-03 16:35:12 +02:00
stick-table
stickiness
stream REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
tcp-rules
webstats MINOR: stats: rename proxy stats 2024-04-22 16:25:18 +02:00
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 ...

  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).

Please note that most tests use a common set of timeouts defined by the
environment variable HAPROXY_TEST_TIMEOUT. As much as possible, for regular I/O
(i.e. not errors), please try to reuse that setting so that the value may
easily be adjusted when running in some particularly slow environments, or be
shortened to fail faster on developers' machines.