haproxy/reg-tests
Christopher Faulet 292619fc90 REGTESTS: log: Reduce again response inspect-delay for last_rule.vtc
It was previously reduced from 10s to 1s but it remains too high, espeically
for the CI. It may be drastically reduced to 100ms. Idea is to just be sure
we will wait for the response before evaluating the TCP rules.
2023-05-17 11:12:25 +02:00
..
balance REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
cache REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 2023-02-22 16:12:45 +01:00
checks REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
compression REGTESTS: Remove REQUIRE_VERSION=1.9 from all tests 2023-01-05 09:11:38 +01:00
connection REGTESTS: remove unsupported "stats bind-process" keyword 2023-04-23 09:44:53 +02:00
contrib REGTESTS: Fix prometheus script to perform HTTP health-checks 2022-08-24 12:17:34 +02:00
converter REGTEST: fix the race conditions in hmac.vtc 2023-01-05 15:22:22 +01:00
filters REGTEESTS: filters: Fix CONNECT request in random-forwarding script 2022-07-07 09:52:56 +02:00
http-capture REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
http-cookies REGTESTS: add test for HTTP/2 cookies concatenation 2022-08-18 16:13:33 +02:00
http-errorfiles REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
http-messaging BUG/MEDIUM: http-ana: Properly switch the request in tunnel mode on upgrade 2023-04-17 16:17:35 +02:00
http-rules REGTESTS : Add test support for case insentitive for url_param 2023-03-30 15:32:14 +02:00
http-set-timeout REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
jwt MINOR: jwt: Add support for RSA-PSS signatures (PS256 algorithm) 2023-03-08 10:43:04 +01:00
log REGTESTS: log: Reduce again response inspect-delay for last_rule.vtc 2023-05-17 11:12:25 +02:00
lua BUG/MEDIUM: tests: use tmpdir to create UNIX socket 2022-12-18 12:47:20 +01:00
mailers REGTESTS: use lua mailer script for mailers tests 2023-05-05 16:28:32 +02:00
mcli REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
peers REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
sample_fetches MINOR: sample: Add bc_rtt and bc_rttvar 2023-04-28 16:31:08 +02:00
seamless-reload REGTESTS: Remove REQUIRE_VERSION=1.8 from all tests 2022-01-29 15:24:45 +01:00
server REGTESTS: add success test, "set server" via fqdn 2023-05-02 11:27:24 +02:00
spoe REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
ssl BUILD: ssl: ssl_c_r_dn fetches uses functiosn only available since 1.1.1 2023-05-15 12:07:52 +02:00
startup REGTESTS: startup: disable automatic_maxconn.vtc 2022-12-16 08:24:04 +01:00
stick-table REGTESTS: fix peers-related regtests regarding "show table" 2022-11-29 16:34:50 +01:00
stickiness REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
stream REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
tcp-rules REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01:00
webstats REGTESTS: webstats: remove unused stats socket in /tmp 2022-04-26 16:15:23 +02:00
README REGTESTS: extend the default I/O timeouts and make them overridable 2021-11-18 17:57:11 +01: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/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.