diff options
Diffstat (limited to 'regress/README.regress')
-rw-r--r-- | regress/README.regress | 31 |
1 files changed, 19 insertions, 12 deletions
diff --git a/regress/README.regress b/regress/README.regress index 6ff032b68..0c07c9cf1 100644 --- a/regress/README.regress +++ b/regress/README.regress | |||
@@ -27,15 +27,26 @@ TEST_SSH_QUIET: set to "yes" to suppress non-fatal output. | |||
27 | TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD | 27 | TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD |
28 | SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER | 28 | SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER |
29 | OBJ: used by test scripts to access build dir. | 29 | OBJ: used by test scripts to access build dir. |
30 | TEST_SHELL: shell used for running the test scripts. | ||
31 | TEST_SSH_PORT: TCP port to be used for the listening tests. | ||
32 | TEST_SSH_SSH_CONFOTPS: Configuration directives to be added to ssh_config | ||
33 | before running each test. | ||
34 | TEST_SSH_SSHD_CONFOTPS: Configuration directives to be added to sshd_config | ||
35 | before running each test. | ||
30 | 36 | ||
31 | 37 | ||
32 | Individual tests. | 38 | Individual tests. |
33 | 39 | ||
34 | You can invoke test-exec.sh directly if you set up the path to find the | 40 | You can run an individual test from the top-level Makefile, eg: |
35 | binaries under test and the test scripts themselves, for example: | 41 | $ make tests LTESTS=agent-timeout |
42 | |||
43 | If you need to manipulate the environment more you can invoke test-exec.sh | ||
44 | directly if you set up the path to find the binaries under test and the | ||
45 | test scripts themselves, for example: | ||
36 | 46 | ||
37 | $ cd regress | 47 | $ cd regress |
38 | $ PATH=`pwd`/..:$PATH:. sh test-exec.sh `pwd` agent-timeout.sh | 48 | $ PATH=`pwd`/..:$PATH:. TEST_SHELL=/bin/sh sh test-exec.sh `pwd` \ |
49 | agent-timeout.sh | ||
39 | ok agent timeout test | 50 | ok agent timeout test |
40 | 51 | ||
41 | 52 | ||
@@ -82,16 +93,12 @@ Failed tests can be difficult to diagnose. Suggestions: | |||
82 | 93 | ||
83 | Known Issues. | 94 | Known Issues. |
84 | 95 | ||
85 | - If you build with tcpwrappers and try to run the regression tests, | ||
86 | your hosts.allow must permit connections from localhost and from | ||
87 | "unknown". This is because some tests are performed via the loopback | ||
88 | interface, while others are done with "sshd -i" as a ProxyCommand. In | ||
89 | the latter case, when sshd calls getpeername() on the socket it will | ||
90 | fail (because it's not a tcp socket) and will be identified as | ||
91 | "unknown", which is then checked against tcpwrappers. | ||
92 | |||
93 | - If your build requires ssh-rand-helper regress tests will fail | 96 | - If your build requires ssh-rand-helper regress tests will fail |
94 | unless ssh-rand-helper is in pre-installed (the path to | 97 | unless ssh-rand-helper is in pre-installed (the path to |
95 | ssh-rand-helper is hard coded). | 98 | ssh-rand-helper is hard coded). |
96 | 99 | ||
97 | $Id: README.regress,v 1.4 2004/03/08 20:12:18 tim Exp $ | 100 | - Recent GNU coreutils deprecate "head -[n]": this will cause the yes-head |
101 | test to fail. The old behaviour can be restored by setting (and | ||
102 | exporting) _POSIX2_VERSION=199209 before running the tests. | ||
103 | |||
104 | $Id: README.regress,v 1.9 2004/08/17 12:31:33 dtucker Exp $ | ||