haproxy/reg-tests
Maxime Henrion 66d5d6a54b REGTESTS: cache: validate the emission of 103s
Add four regtests to validate the behavior of the HTTP cache when early
hints are enabled.

- early_hints.vtc: covers 103 emission on stripped entries and that the
  "no-early-hints" rule keyword suppresses it.
- early_hints_ratio.vtc: covers cap-driven eviction of hints entries when
  the ratio is reached.
- early_hints_parsing.vtc: pins down the (deliberately strict) Link
  header parsing behaviour of link_is_hint() so future relaxations
  cannot silently change hint detection.
- early_hints_multiblock.vtc: checks that hints are still extracted when
  the relevant Link headers span more than one cache block.
2026-07-10 16:42:35 +02:00
..
balance BUG/MAJOR: lb-chash: fix key calculation when using default hash-key id 2025-10-16 10:43:09 +02:00
cache REGTESTS: cache: validate the emission of 103s 2026-07-10 16:42:35 +02:00
checks REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
compression REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
connection REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
contrib REGTESTS: Migrate REQUIRE_SERVICE=prometheus-exporter to a feature(PROMEX) check 2026-07-08 14:50:25 +02:00
converter REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
filters REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
http-capture REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
http-cookies REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
http-errorfiles REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
http-messaging BUG/MINOR: h1: Don't mask websocket protocol if multiple protocols used 2026-05-19 17:50:50 +02:00
http-rules REGTESTS: Improve script testing the set-timeout action 2026-07-08 08:52:07 +02:00
jwt MINOR: jwe: Disable 'RSA1_5' algorithm by default in jwt_decrypt converters 2026-05-07 18:00:29 +02:00
log REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
lua REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
mailers REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
mcli Revert "BUG/MEDIUM: cli: fix master CLI connection slot leak on client disconnect" 2026-05-07 16:37:33 +02:00
peers REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
pki REGTESTS: pki: add a pki for SSL tests 2023-10-09 21:54:31 +02:00
proxy MINOR: proxy: remove the experimental status on dynamic backends 2026-05-19 14:56:45 +02:00
qmux REGTESTS: add basic QMux tests 2026-06-02 13:31:15 +02:00
quic REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
sample_fetches REGTESTS: explicitly use "balance roundrobin" where RR is needed 2025-09-04 08:18:53 +02:00
seamless-reload REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
server REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
spoe REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
ssl REGTESTS: Migrate REQUIRE_OPTION to haproxy -cc 2026-07-08 14:50:25 +02:00
startup REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
stats MEDIUM: stats: add persistent state to typed output format 2025-07-01 14:15:03 +02:00
stick-table REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
stickiness REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
stream MINOR: stream: Add be_max_retries/cur_max_retries sample fetch functions 2026-07-08 08:52:07 +02:00
tcp-rules REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
webstats REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02: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.