haproxy/reg-tests
Willy Tarreau 5c15ba5eff MEDIUM: proxy: mark the "dispatch" directive as deprecated
As mentioned in [1], the "dispatch" directive from haproxy 1.0 has long
outlived its original purpose and still suffers from a number of technical
limitations (no checks, no SSL, no idle connes etc) and still hinders some
internal evolutions. It's now time to mark it as deprecated, and to remove
it in 3.5 [2]. It was already recommended against in the documentation but
remained popular in raw TCP environments for being shorter to write.

The directive will now cause a warning to be emitted, suggesting an
alternate method involving "server". The warning can be shut using
"expose-deprecated-directives". The rare configs from 1.0 where
"dispatch" is combined with sticky servers using cookies will just
need to set these servers's weights to zero to prevent them from
being selected by the load balancing algorithm. All of this is
explained in the doc with examples.

Two reg tests were using this method, one purposely for this directive,
which now has expose-deprecated-directives, and another one to test the
behavior of idle connections, which was updated to use "server" and
extended to test both "http-reuse never" and "http-reuse always".

[1] https://github.com/orgs/haproxy/discussions/2921
[2] https://github.com/haproxy/wiki/wiki/Breaking-changes
2025-06-26 15:29:47 +02:00
..
balance REGTESTS: Remove REQUIRE_VERSION=2.3 from all tests 2025-06-02 17:37:00 +02:00
cache REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
checks REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
compression CLEANUP: assorted typo fixes in the code and comments 2025-04-02 11:12:20 +02:00
connection MEDIUM: proxy: mark the "dispatch" directive as deprecated 2025-06-26 15:29:47 +02:00
contrib REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
converter REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
filters REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
http-capture REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-cookies REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-errorfiles REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-messaging REGTESTS: Remove tests with REQUIRE_VERSION_BELOW=2.4 2025-06-02 17:37:07 +02:00
http-rules REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
http-set-timeout REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
jwt REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
log REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
lua REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
mailers MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion" 2024-12-20 17:34:05 +01:00
mcli MAJOR: mworker: remove program section support 2025-06-25 16:11:34 +02:00
peers REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
pki REGTESTS: pki: add a pki for SSL tests 2023-10-09 21:54:31 +02:00
sample_fetches REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
seamless-reload REGTESTS: switch to -Ws for master-worker reg-tests 2024-11-20 17:13:59 +01:00
server REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
spoe REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
ssl REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
startup REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
stats REGTESTS: add missing timeouts to 30 tests 2024-11-19 08:46:02 +01:00
stick-table REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
stickiness REGTESTS: Remove REQUIRE_VERSION=2.4 from all tests 2025-06-02 17:37:04 +02:00
stream REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
tcp-rules REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
webstats REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
README CI: vtest: Rely on VTest2 to run regression tests 2025-05-27 14:38:46 +02:00

                 * 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/VTest2

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