1Test Suite for Rivet
2====================
3
4$Id$
5
6These tests are intended to automate the testing of core Rivet
7features.  They are not complete at this point, and work on them would
8be welcome.
9
10How to run the tests:
11--------------------
12
13The program 'runtest.tcl' is launched with the full path to the apache
14web server.  It then creates a minimal config file in the directory it
15is launched from, and launches Apache with the generated config.  We
16are thusly able to manipulate the environment completely, and run the
17tests directly in the tests/ directory...
18
19Note that either mod_so.c (to load Rivet as DSO) or Rivet itself must
20be compiled into Apache for this to work.
21
22For example:
23
24./runtest.tcl /usr/sbin/apache
25
26Where to put tests/which files are which:
27----------------------------------------
28
29binary.test: Test whether an image file comes through ok.
30
31broken.test: Test whether a broken page displays an error message
32	     correctly.
33
34config.test: Test different configuration combinations.
35
36cookies.test: Test whether cookies work.
37
38env.test: See if 'environmental' variables are coming through alright.
39
40get.test: Test whether a simple GET works with variables
41	  (i.e. ?foo=1&bar=2)
42
43hello.test: Test whether a simple hello world page works.
44
45include.test: Test whether flat file includes work.
46
47lang.test: Try some japanese encodings, to see if they come through
48	   ok.
49
50makeurl.test: Test whether the 'makeurl' command works.
51
52parse.test: Test whether the 'parse' command is able to correctly
53	    parse and utilize a second .rvt file.
54
55post.test: See if POST works ok.
56
57rivet.test: This starts the tests up and runs them.
58
59tclfile.test: Make sure that Rivet works ok with a plain .tcl file.
60
61upload.test: Check whether file uploads work.
62