haproxy/reg-tests
Aurelien DARRAGON 29b6d8af16 MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion"
A better name was found for the option implemented in ec74438
("MINOR: hlua: add option to preserve bool type from smp to lua")

Indeed, "tune.lua.preserve-smp-bool {on | off}" wasn't explicit enough
nor did it encourage the adoption of the new "fixed" behavior (vs
historical behavior which is now considered as a bug).

Thus it becomes "tune.lua.bool-sample-conversion { normal | pre-3.1-bug }"
which actively encourage users to switch the new behavior after having
patched in-use Lua script if needed. From a technical point of view,
the logic remains the same, as the option currently defaults to
"pre-3.1-bug" to prevent script breakage, and a warning is emitted if
the option isn't set explicily and Lua is used.

Documentation and regtests were updated.

Must be backported in 3.1 with ec74438 and f2838f5 ("REGTESTS: fix
lua-based regtests using tune.lua.smp-preserve-bool")
2024-12-20 17:34:05 +01:00
..
balance REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
cache REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
checks REGTESTS: relax strerror matching to avoid a failure on libmusl 2024-11-21 20:26:46 +01:00
compression MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion" 2024-12-20 17:34:05 +01:00
connection REGTESTS: disable temporarly mworker test on OSX 2024-11-20 17:13:59 +01:00
contrib REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
converter REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
filters REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-capture REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-cookies REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-errorfiles REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-messaging REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
http-rules REGTESTS: disable temporarly mworker test on OSX 2024-11-20 17:13:59 +01:00
http-set-timeout REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
jwt REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
log REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
lua MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion" 2024-12-20 17:34:05 +01:00
mailers MINOR: hlua: rename "tune.lua.preserve-smp-bool" to "tune.lua.bool-sample-conversion" 2024-12-20 17:34:05 +01:00
mcli REGTESTS: disable temporarly mworker test on OSX 2024-11-20 17:13:59 +01:00
peers REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
pki
sample_fetches REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
seamless-reload REGTESTS: switch to -Ws for master-worker reg-tests 2024-11-20 17:13:59 +01:00
server REGTESTS: switch to -Ws for master-worker reg-tests 2024-11-20 17:13:59 +01:00
spoe REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
ssl REGTESTS: ssl: add a PEM with mix of LF and CRLF line endings 2024-12-13 18:13:42 +01:00
startup REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
stats REGTESTS: add missing timeouts to 30 tests 2024-11-19 08:46:02 +01:00
stick-table REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
stickiness REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
stream REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
tcp-rules REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
webstats REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +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.