.. _ref-varnishtest: =========== varnishtest =========== ------------------------ Test program for Varnish ------------------------ SYNOPSIS ======== varnishtest [-iklLqv] [-n iter] [-D name=val] [-j jobs] [-t duration] file [file ...] DESCRIPTION =========== The varnishtest program is a script driven program used to test the Varnish Cache. The varnishtest program, when started and given one or more script files, can create a number of threads representing backends, some threads representing clients, and a varnishd process. This is then used to simulate a transaction to provoke a specific behavior. The following options are available: -D name=val Define macro for use in scripts -i Find varnishd in build tree -j jobs Run this many tests in parallel -k Continue on test failure -l Leave temporary vtc.* if test fails -L Always leave temporary vtc.* -n iterations Run tests this many times -q Quiet mode: report only failures -t duration Time tests out after this long -v Verbose mode: always report test log -h Show help file File to use as a script Macro definitions that can be overridden. varnishd Path to varnishd to use [varnishd] If `TMPDIR` is set in the environment, varnishtest creates temporary `vtc.*` directories for each test in `$TMPDIR`, otherwise in `/tmp`. SCRIPTS ======= The script language used for Varnishtest is not a strictly defined language. The best reference for writing scripts is the varnishtest program itself. In the Varnish source code repository, under `bin/varnishtest/tests/`, all the regression tests for Varnish are kept. An example:: varnishtest "#1029" server s1 { rxreq expect req.url == "/bar" txresp -gzipbody {[bar]} rxreq expect req.url == "/foo" txresp -body {