Test-scripts for varnishtest
============================

Naming scheme
-------------

	The intent is to be able to run all scripts in lexicographic
	order and get a sensible failure mode.

	This requires more basic tests to be earlier and more complex
	tests to be later in the test sequence, we do this with the
	prefix/id letter:

		[id]%05d.vtc

	id ~ ^a		--> varnishtest(1) tests
	id ~ ^a02	--> HTTP2
	id ~ ^b		--> Basic functionality tests
	id ~ ^c		--> Complex functionality tests
	id ~ ^d		--> Director facility tests
	id ~ ^e		--> ESI tests
	id ~ ^f		--> Security related tests
	id ~ ^g		--> GZIP tests
	id ~ ^h		--> HAproxy tests
	id ~ ^i		--> Interoperability and standards compliance
	id ~ ^j		--> JAIL tests
	id ~ ^l		--> VSL tests
	id ~ ^m		--> VMOD facility, vmod_debug and vmod_vtc
	id ~ ^o		--> prOxy protocol
	id ~ ^p		--> Persistent tests
	id ~ ^r		--> Regression tests, same number as ticket
	id ~ ^s		--> Slow tests, expiry, grace etc.
	id ~ ^t		--> Transport protocol tests
	id ~ ^t02	--> HTTP2
	id ~ ^u		--> Utilities and background processes
	id ~ ^v		--> VCL tests: execute VRT functions
	id ~ ^x		--> VEXT tests

	Coverage for individual VMODs is in "${top_srcdir}vmod/tests".

Tests suffixed with .disabled are not executed automatically on 'make check'.

The main reason for a test to live here is when the underlying problem
isn't fixed yet, but a test case exists. This avoids breaking the rest of
the 'make check' tests while a fix is being produced.
