haproxy/reg-tests
Alexander Stephan 4949b0a9a7 REGTESTS: server: add test for 'set server name' CLI command
Tests cover:
  - error cases: missing name, not-in-maintenance, invalid chars
    (rejected by invalid_char()), duplicate name in the same backend,
    name-referenced server (use-server target, track target)
  - same-name rename as a no-op success
  - successful rename with verification via 'show servers state'
  - old name no longer resolves after rename
  - round-trip rename back to original name
  - traffic still works after rename round-trip

The use-server and tracked-server cases exercise the SRV_F_NAME_REFD
gating added in the preceding patch. Servers pinned only via resolvers
(SRV_F_NON_PURGEABLE without SRV_F_NAME_REFD) remain renamable; that
positive case is not exercised here as it would require a real DNS
resolver in the test environment.
2026-07-01 09:32:30 +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: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
checks REGTESTS: Fix log matching in healthcheck-section.vtc 2026-06-09 08:42:01 +02:00
compression REGTESTS: ssl: Move all the SSL certificates, keys, crt-lists inside "certs" directory 2025-12-08 10:40:59 +01:00
connection MAJOR: proxy: remove support for "dispatch" and "transparent" proxy keywords 2026-06-26 10:51:16 +02:00
contrib REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
converter MINOR: sample: add a reverse_dom converter 2026-05-13 16:49:53 +02:00
filters REGTESTS: add a test for "filter-sequence" directive 2026-04-03 12:10:32 +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 REG-TESTS: map_redirect: Don't use hdr_dom in ACLs with "-m end" matching method 2025-09-01 15:45:05 +02:00
http-set-timeout REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +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 MEDIUM: httpclient/lua: allow multiple requests from a single core.httpclient() instance 2026-06-14 01:49:54 +02:00
mailers REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +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: ssl: Move all the SSL certificates, keys, crt-lists inside "certs" directory 2025-12-08 10:40:59 +01: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: quic: test H3 request without content-length 2026-06-24 08:53:04 +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: server: add test for 'set server name' CLI command 2026-07-01 09:32:30 +02:00
spoe REGTESTS: restrict execution to a single thread group 2025-06-30 18:54:35 +02:00
ssl REGTESTS: quic/issuers_chain_path: do not forget to enable QUIC compat mode 2026-05-18 18:01:53 +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 MEDIUM: proxy: force traffic on unpublished/disabled backends 2026-01-15 09:08:19 +01: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.