| README.regress (128456) | README.regress (137015) |
|---|---|
| 1Overview. 2 3$ ./configure && make tests 4 5You'll see some progress info. A failure will cause either the make to 6abort or the driver script to report a "FATAL" failure. 7 8The test consists of 2 parts. The first is the file-based tests which is --- 13 unchanged lines hidden (view full) --- 22 23SUDO: path to sudo command, if desired. Note that some systems (notably 24 systems using PAM) require sudo to execute some tests. 25TEST_SSH_TRACE: set to "yes" for verbose output from tests 26TEST_SSH_QUIET: set to "yes" to suppress non-fatal output. 27TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD 28 SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER 29OBJ: used by test scripts to access build dir. | 1Overview. 2 3$ ./configure && make tests 4 5You'll see some progress info. A failure will cause either the make to 6abort or the driver script to report a "FATAL" failure. 7 8The test consists of 2 parts. The first is the file-based tests which is --- 13 unchanged lines hidden (view full) --- 22 23SUDO: path to sudo command, if desired. Note that some systems (notably 24 systems using PAM) require sudo to execute some tests. 25TEST_SSH_TRACE: set to "yes" for verbose output from tests 26TEST_SSH_QUIET: set to "yes" to suppress non-fatal output. 27TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD 28 SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER 29OBJ: used by test scripts to access build dir. |
| 30TEST_SHELL: shell used for running the test scripts. 31TEST_SSH_PORT: TCP port to be used for the listening tests. 32TEST_SSH_SSH_CONFOTPS: Configuration directives to be added to ssh_config 33 before running each test. 34TEST_SSH_SSHD_CONFOTPS: Configuration directives to be added to sshd_config 35 before running each test. |
|
| 30 31 32Individual tests. 33 | 36 37 38Individual tests. 39 |
| 34You can invoke test-exec.sh directly if you set up the path to find the 35binaries under test and the test scripts themselves, for example: | 40You can run an individual test from the top-level Makefile, eg: 41$ make tests LTESTS=agent-timeout |
| 36 | 42 |
| 43If you need to manipulate the environment more you can invoke test-exec.sh 44directly if you set up the path to find the binaries under test and the 45test scripts themselves, for example: 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 |
| 39ok agent timeout test 40 41 42Files. 43 44test-exec.sh: the main test driver. Sets environment, creates config files 45and keys and runs the specified test. 46 --- 30 unchanged lines hidden (view full) --- 77Failed tests can be difficult to diagnose. Suggestions: 78- run the individual test via ./test-exec.sh `pwd` [testname] 79- set LogLevel to VERBOSE in test-exec.sh and enable syslogging of 80 auth.debug (eg to /var/log/authlog). 81 82 83Known Issues. 84 | 50ok agent timeout test 51 52 53Files. 54 55test-exec.sh: the main test driver. Sets environment, creates config files 56and keys and runs the specified test. 57 --- 30 unchanged lines hidden (view full) --- 88Failed tests can be difficult to diagnose. Suggestions: 89- run the individual test via ./test-exec.sh `pwd` [testname] 90- set LogLevel to VERBOSE in test-exec.sh and enable syslogging of 91 auth.debug (eg to /var/log/authlog). 92 93 94Known Issues. 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 94 unless ssh-rand-helper is in pre-installed (the path to 95 ssh-rand-helper is hard coded). 96 | 96- If your build requires ssh-rand-helper regress tests will fail 97 unless ssh-rand-helper is in pre-installed (the path to 98 ssh-rand-helper is hard coded). 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 $ |