haproxy/reg-tests
Willy Tarreau 9d511b3c27 REGTESTS: enable -dW on almost all tests to fail on warnings
Now that warnings were almost all removed, let's enable zero-warning
via -dW. All tests were adjusted, but two:

  - mcli/mcli_start_progs.vtc:
      the programs section currently cannot be silenced

  - stats/stats-file.vtc:
      the warning comes from the stats file itself on comment lines.

All other ones are now OK.
2024-11-19 09:27:08 +01:00
..
balance REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
cache REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
checks REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
compression REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
connection REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
contrib REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
converter REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
filters REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-capture REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-cookies REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-errorfiles REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-messaging REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-rules REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
http-set-timeout REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
jwt REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
log REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
lua REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
mailers REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
mcli REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
peers REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
pki REGTESTS: pki: add a pki for SSL tests 2023-10-09 21:54:31 +02:00
sample_fetches REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
seamless-reload REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
server REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
spoe REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
ssl REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
startup REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
stats REGTESTS: add missing timeouts to 30 tests 2024-11-19 08:46:02 +01:00
stick-table REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
stickiness REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
stream REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
tcp-rules REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01:00
webstats REGTESTS: enable -dW on almost all tests to fail on warnings 2024-11-19 09:27:08 +01: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.