haproxy/reg-tests
Tristan 18582ede05 MEDIUM: socket: add zero-terminated ABNS alternative
When an abstract unix socket is bound by HAProxy (using "abns@" prefix),
NUL bytes are appended at the end of its path until sun_path is filled
(for a total of 108 characters).

Here we add an alternative to pass only the non-NUL length of that path
to connect/bind calls, such that the effective path of the socket's name
is as humanly written. This may be useful to interconnect with existing
softwares that implement abstract sockets with this logic instead of the
default haproxy one.

This is achieved by implementing the "abnsz" socket prefix (instead of
"abns"), which stands for "zero-terminated ABNS". "abnsz" prefix may be
used anywhere "abns" is. Internally, haproxy uses the custom socket
family (AF_CUST_ABNS vs AF_CUST_ABNSZ) to differentiate default abns
sockets from zero-terminated ones.

Documentation was updated and regtest was added.

Fixes GH issues #977 and #2479

Co-authored-by: Aurelien DARRAGON <adarragon@haproxy.com>
2024-10-29 12:15:24 +01:00
..
balance
cache REGTESTS: cache: Add test on 'vary' other than accept-encoding 2024-04-29 10:41:48 +02:00
checks MINOR: tcpcheck: Add support for an option host header value for httpchk option 2024-10-02 10:22:51 +02:00
compression
connection REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
contrib REGTESTS: Do not use REQUIRE_VERSION for HAProxy 2.5+ (4) 2024-04-02 07:27:33 +02:00
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: cli: add delay 0.1 before connect to cli 2024-10-16 22:00:58 +02:00
http-set-timeout
jwt
log REGTESTS: add some tests for 'do-log' action 2024-10-04 21:38:19 +02: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: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
seamless-reload REGTESTS: fix a reload race in abns_socket.vtc 2024-10-14 19:15:21 +02:00
server MEDIUM: socket: add zero-terminated ABNS alternative 2024-10-29 12:15:24 +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 REGTESTS: startup: -conf-OK requires -V with current VTest 2023-11-13 14:57:26 +01:00
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

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.