haproxy/reg-tests
William Lallemand c268313f60 REGTESTS: ssl: activate new SSL reg-tests with AWS-LC
Prerequisites are now available in AWS-LC, so we can enable these
reg-tests.

With this patch, aws-lc only has 5 reg-tests that are not working:
- reg-tests/ssl/ssl_reuse.vtc: stateful session resumption is only supported with TLSv1.2
- reg-tests/ssl/ssl_curve_name.vtc: function to extract curve name is not available
- reg-tests/ssl/ssl_errors.vtc: errors are not the same than OpenSSL
- reg-tests/ssl/ssl_dh.vtc: AWS-LC does not support DH
- reg-tests/ssl/ssl_curves.vtc: not working correctly

Which means most of the features are working correctly.
2024-06-17 17:43:22 +02:00
..
balance
cache REGTESTS: cache: Add test on 'vary' other than accept-encoding 2024-04-29 10:41:48 +02:00
checks REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
compression MINOR: compression: Improve the way Vary header is added 2023-05-25 11:25:31 +02:00
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 REGTESTS: filters: Don't set C-L header in the successful response to CONNECT 2023-10-04 15:34:18 +02:00
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: ssl: fix some regtests 'feature cmd' start condition 2024-06-17 16:12:57 +02:00
http-rules REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
http-set-timeout MINOR: support for http-response set-timeout 2023-10-17 08:27:33 +02:00
jwt
log REGTESTS: log: add a test for log-profile 2024-06-13 15:43:10 +02:00
lua REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
mailers REGTESTS: use lua mailer script for mailers tests 2023-05-05 16:28:32 +02:00
mcli
peers
pki REGTESTS: pki: add a pki for SSL tests 2023-10-09 21:54:31 +02:00
sample_fetches REGTESTS: Remove REQUIRE_VERSION=2.2 from all tests 2024-05-29 22:36:15 +02:00
seamless-reload REGTESTS: try to activate again the seamless reload test with the master CLI 2023-11-17 17:11:42 +01:00
server REGTESTS: ssl: update common.pem with the new pki 2023-10-09 21:58:21 +02:00
spoe MAJOR: spoe: Let the SPOE back into the game 2024-05-22 09:04:38 +02:00
ssl REGTESTS: ssl: activate new SSL reg-tests with AWS-LC 2024-06-17 17:43:22 +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 REG-TESTS: stickiness: Delay haproxys start to properly resolv variables 2023-06-05 08:24:34 +02:00
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

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