annotate tests/README @ 249:f9da5a7caeda
refactored the cmdline argument processing
I replaced the nested switch statements with one single
large else-if construct. Instead of char comparision now
str(n)cmp(3) is used. Although this is slower it is much
more readable and covers corner-cases which were uncovered
before (e.g. -bdxxx).
As always: Readability and simplicity matter, not performance.
author |
markus schnalke <meillo@marmaro.de> |
date |
Thu, 04 Nov 2010 11:02:42 -0300 |
parents |
49ca781e1503 |
children |
|
rev |
line source |
meillo@63
|
1 This directory contains test cases for masqmail, one in each directory.
|
meillo@0
|
2
|
meillo@63
|
3 Build the test scripts be running
|
meillo@63
|
4 make
|
meillo@63
|
5 in the directory. You can build all of them by running
|
meillo@63
|
6 make
|
meillo@63
|
7 in the tests directory.
|
meillo@0
|
8
|
meillo@63
|
9 Run the test by executing
|
meillo@63
|
10 ./test
|
meillo@63
|
11 in its directory, preferably NOT as root, but you got to have write
|
meillo@63
|
12 permission for the directory.
|
meillo@0
|
13
|
meillo@0
|
14
|
meillo@63
|
15 Usually, two log files, masqmail.log and debug.log, will be created.
|
meillo@63
|
16 They may give some information if anything went wrong.
|
meillo@0
|
17
|
meillo@63
|
18 The README files in the test case directories explain the tests in
|
meillo@63
|
19 more detail.
|
meillo@0
|
20
|
meillo@0
|
21
|
meillo@63
|
22 FIXME: Currently, the return values of the test scripts don't express
|
meillo@63
|
23 if the test was successful or not.
|
meillo@0
|
24
|
meillo@63
|
25
|
meillo@63
|
26 If tests do not work, there could be some problem with either the test
|
meillo@0
|
27 programs, the configuration file or masqmail itself. If you have
|
meillo@0
|
28 installed masqmail successfully and these scripts do not work, do not
|
meillo@0
|
29 worry too much :-).
|
meillo@64
|
30
|
meillo@64
|
31
|
meillo@64
|
32 The original test scripts are by oku.
|
meillo@64
|
33 They were rearranged and extended by meillo.
|