haproxy/reg-tests
Christopher Faulet 8acb1284bc MINOR: checks: Add a way to send custom headers and payload during http chekcs
The 'http-check send' directive have been added to add headers and optionnaly a
payload to the request sent during HTTP healthchecks. The request line may be
customized by the "option httpchk" directive but there was not official way to
add extra headers. An old trick consisted to hide these headers at the end of
the version string, on the "option httpchk" line. And it was impossible to add
an extra payload with an "http-check expect" directive because of the
"Connection: close" header appended to the request (See issue #16 for details).

So to make things official and fully support payload additions, the "http-check
send" directive have been added :

    option httpchk POST /status HTTP/1.1

    http-check send hdr Content-Type "application/json;charset=UTF-8" \
        hdr X-test-1 value1 hdr X-test-2 value2 \
        body "{id: 1, field: \"value\"}"

When a payload is defined, the Content-Length header is automatically added. So
chunk-encoded requests are not supported yet. For now, there is no special
validity checks on the extra headers.

This patch is inspired by Kiran Gavali's work. It should fix the issue #16 and
as far as possible, it may be backported, at least as far as 1.8.
2020-04-27 09:39:37 +02:00
..
cache
checks MINOR: checks: Add a way to send custom headers and payload during http chekcs 2020-04-27 09:39:37 +02:00
compression REGTESTS: use "command -v" instead of "which" 2020-02-18 14:45:22 +01:00
connection REGTEST: make the PROXY TLV validation depend on version 2.2 2020-03-31 16:37:58 +02:00
converter MINOR: sample: Validate the number of bits for the sha2 converter 2019-12-17 13:28:00 +01:00
http-capture
http-cookies
http-errorfiles CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
http-messaging MINOR: http-htx: Move htx sample fetches in the scope "internal" 2020-01-20 15:18:45 +01:00
http-rules REGTESTS: Add a reg test for http-after-response rulesets 2020-02-06 15:13:04 +01:00
log REGTEST: Wrong assumption in IP:port logging test. 2019-05-07 13:58:35 +02:00
lua
mailers CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
mcli REGTEST: mcli/mcli_start_progs: start 2 programs 2020-01-14 15:42:38 +01:00
peers REGTESTS: Send valid URIs in peers reg-tests and fix HA config to avoid warnings 2019-10-14 22:28:50 +02:00
sample_fetches MINOR: listener: add so_name sample fetch 2020-03-29 05:47:29 +02:00
seamless-reload REGTEST: increase timeouts on the seamless-reload test 2020-03-23 09:11:51 +01:00
server REGTESTS: server/cli_set_fqdn requires version 1.8 minimum 2019-10-22 13:06:59 +02:00
spoe CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
ssl REGTEST: ssl/cli: add other cases of 'add ssl crt-list' 2020-04-02 15:40:19 +02:00
stick-table
stickiness REGTEST: Add a basic server by name stickiness reg test. 2019-06-05 08:42:36 +02:00
stream REGTEST: make the unique-id test depend on version 2.0 2020-04-01 16:08:43 +02:00
webstats
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 [-Dno-htx=] ...

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