Mercurial > hg > nginx-tests

comparison README @ 26:0880e0fafde4

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Tests: implement smtp test backend and use it.
author Maxim Dounin <mdounin@mdounin.ru>
date Thu, 02 Oct 2008 16:18:11 +0400
parents 1059c3002030
children 71ea39729fa0
comparison
equal deleted inserted replaced
25:fbda19df2fc4 26:0880e0fafde4
1 Test suit for nginx. 1 Test suit for nginx.
2 2
3 Use prove to run tests as one usually do for perl tests. Individual tests 3 Use prove to run tests as one usually do for perl tests. Individual tests
4 may be run as well. 4 may be run as well.
5 5
6 Tests assume that nginx sources are in directory nginx at the same level
7 as directory with tests, and nginx was already configured and built (i.e.
8 nginx binary available as ../nginx/objs/nginx from test directory).
9
6 Note: some tests may fail since they are for bugs not fixed in public code. 10 Note: some tests may fail since they are for bugs not fixed in public code.
7 11
8 Note: tests run nginx listening on localhost, and currently this includes 12 Note: tests run nginx listening on localhost, and currently this includes
9 following ports: 8080, 10025. 13 following ports: 8025, 8026, 8080, 8081.
10 14
11 Currently each test creates it's own temporary directory and uses it for 15 Currently each test creates it's own temporary directory and uses it for
12 logs etc. One may instruct tests not to remove the temp directory (e.g. 16 logs etc. One may instruct tests not to remove the temp directory (e.g.
13 for analysis of failed test) by setting LEAVE environment variable. 17 for analysis of failed test) by setting LEAVE environment variable.