Mercurial > masqmail-0.2

comparison tests/README @ 63:49ca781e1503

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
reworked the test cases completely they are split into four independent tests now and each one is tested to work with the current version
author meillo@marmaro.de
date Sun, 30 May 2010 16:05:49 +0200
parents 08114f7dcc23
children 0379789a847b
comparison
equal deleted inserted replaced
62:610cd4e09b91 63:49ca781e1503
1 Here a two test programs: local.sh and smtpout.sh. They both send 1 This directory contains test cases for masqmail, one in each directory.
2 three mails, using different options. Run them from within this
3 directory, preferably NOT as root, but you got to have write
4 permission for this directory.
5 2
6 local.sh sends mail accepted from stdin and sends them to a fake local 3 Build the test scripts be running
7 mailbox, using your login name. If it works, there should be a file 4 make
8 named with your login name with the mails. You can look at it with cat 5 in the directory. You can build all of them by running
9 or less, or with an ordinary mail program. 6 make
7 in the tests directory.
10 8
11 smtpout.sh sends mail accepted from stdin and sends them to your local 9 Run the test by executing
12 MTA, so use it only if you have an MTA running on your box (sendmail, 10 ./test
13 exim, qmail or whatever, or masqmail when you have it already 11 in its directory, preferably NOT as root, but you got to have write
14 installed). If it works, you should get three mails. 12 permission for the directory.
15 13
16 The scripts assume that your login name corresponds to your mailbox
17 (quite probable) and that your MTA listens on port 25 with the
18 interface which corresponds to the hostname as returned by the shell
19 command "hostname" (without quotes...), also very probable. They are
20 created with make from test.templ. They use a special configuration
21 (test.conf) for masqmail, which is also created with make from
22 conf.templ.
23 14
24 Two log files, masqmail.log and debug.log will also be created within 15 Usually, two log files, masqmail.log and debug.log, will be created.
25 this directory. They may give some information if anything went wrong. 16 They may give some information if anything went wrong.
26 17
27 If the log files reveal that your MTA is not willing to relay, you may 18 The README files in the test case directories explain the tests in
28 have to qualify the hostname: Say 19 more detail.
29 20
30 sed s/RECV_HOST/foo.bar.com/ test.templ > smtpout.sh
31 21
32 where you set your fully qualified host name for foo.bar.com. 22 FIXME: Currently, the return values of the test scripts don't express
23 if the test was successful or not.
33 24
34 If they do not work, there could be some problem with either the test 25
26 If tests do not work, there could be some problem with either the test
35 programs, the configuration file or masqmail itself. If you have 27 programs, the configuration file or masqmail itself. If you have
36 installed masqmail successfully and these scripts do not work, do not 28 installed masqmail successfully and these scripts do not work, do not
37 worry too much :-). 29 worry too much :-).