openssh/regress
Damien Miller 89437edafd - (djm) [regress/sftp-cmds.sh]
Use more restrictive glob to pick up test files from /bin - some platforms
   ship broken symlinks there which could spoil the test.
2007-10-26 15:37:50 +10:00
..
.cvsignore - (djm) [regress/.cvsignore] Ignore Makefile here 2006-03-15 13:13:27 +11:00
agent-getpeereid.sh - (dtucker) [regress/agent-getpeereid.sh] Do peereid test if we have 2007-03-21 21:45:48 +11:00
agent-ptrace.sh - (dtucker) [regress/agent-ptrace.sh] Make ttrace gdb error a little more 2007-03-03 09:42:23 +11:00
agent-timeout.sh
agent.sh
banner.sh - dtucker@cvs.openbsd.org 2003/10/11 11:49:49 2004-01-30 12:58:51 +11:00
broken-pipe.sh
brokenkeys.sh - djm@cvs.openbsd.org 2004/10/29 23:59:22 2004-12-06 23:07:37 +11:00
bsd.regress.mk
cfgmatch.sh - dtucker@cvs.openbsd.org 2006/12/13 08:36:36 2007-10-26 14:45:13 +10:00
cipher-speed.sh - pvalchev@cvs.openbsd.org 2007/06/07 19:41:46 2007-10-26 14:45:57 +10:00
connect-privsep.sh
connect.sh
dsa_ssh2.prv
dsa_ssh2.pub
dynamic-forward.sh Resync Ids 2004-12-06 22:58:11 +11:00
envpass.sh - djm@cvs.openbsd.org 2005/03/04 08:48:46 2005-03-07 18:35:34 +11:00
exit-status.sh
forcecommand.sh - (dtucker) [regress/forcecommand.sh] Portablize. 2006-07-24 23:50:23 +10:00
forwarding.sh - (djm) [regress/Makefile regress/agent-getpeereid.sh regress/cfgmatch.sh] 2006-07-24 15:31:41 +10:00
keygen-change.sh
keyscan.sh
login-timeout.sh - djm@cvs.openbsd.org 2005/02/27 23:13:36 2005-03-07 18:34:04 +11:00
Makefile - (djm) [regress/Makefile regress/agent-getpeereid.sh regress/cfgmatch.sh] 2006-07-24 15:31:41 +10:00
multiplex.sh - dtucker@cvs.openbsd.org 2005/04/25 09:54:09 2006-01-31 21:57:27 +11:00
proto-mismatch.sh
proto-version.sh
proxy-connect.sh
README.regress - (dtucker) [regress/README.regress] Bug #989: Document limitation that scp 2005-10-03 20:14:18 +10:00
reconfigure.sh - (dtucker) [regress/reconfigure.sh] Fix potential race in the reconfigure 2005-11-12 21:30:07 +11:00
reexec.sh - (dtucker) [regress/reexec.sh] Add ${EXEEXT} so this test also works on 2005-05-26 13:43:57 +10:00
rekey.sh - (dtucker) [regress/rekey.sh] Touch datafile before filling with dd, since 2004-12-20 12:35:42 +11:00
rsa_openssh.prv
rsa_openssh.pub
rsa_ssh2.prv
runtests.sh
scp-ssh-wrapper.sh - dtucker@cvs.openbsd.org 2005/12/14 04:36:39 2006-01-31 22:03:11 +11:00
scp.sh - djm@cvs.openbsd.org 2006/01/31 10:36:33 2006-01-31 22:06:41 +11:00
sftp-badcmds.sh [Makefile.in regress/sftp-badcmds.sh regress/test-exec.sh] 2004-02-12 07:17:10 -08:00
sftp-batch.sh - djm@cvs.openbsd.org 2004/01/13 09:49:06 2004-01-30 13:02:55 +11:00
sftp-cmds.sh - (djm) [regress/sftp-cmds.sh] 2007-10-26 15:37:50 +10:00
sftp-glob.sh - djm@cvs.openbsd.org 2007/10/26 05:30:01 2007-10-26 15:35:54 +10:00
sftp.sh
ssh-com-client.sh - markus@cvs.openbsd.org 2004/02/24 17:06:52 2004-02-29 20:33:51 +11:00
ssh-com-keygen.sh - markus@cvs.openbsd.org 2004/02/24 17:06:52 2004-02-29 20:33:51 +11:00
ssh-com-sftp.sh - markus@cvs.openbsd.org 2004/02/24 17:06:52 2004-02-29 20:33:51 +11:00
ssh-com.sh - markus@cvs.openbsd.org 2004/02/24 17:06:52 2004-02-29 20:33:51 +11:00
sshd-log-wrapper.sh - dtucker@cvs.openbsd.org 2005/02/27 11:33:30 2005-03-07 18:33:02 +11:00
stderr-after-eof.sh
stderr-data.sh
t4.ok
t5.ok
test-exec.sh - djm@cvs.openbsd.org 2007/10/26 05:30:01 2007-10-26 15:35:54 +10:00
transfer.sh
try-ciphers.sh - pvalchev@cvs.openbsd.org 2007/06/07 19:41:46 2007-10-26 14:45:57 +10:00
yes-head.sh - (dtucker) [regress/yes-head.sh] Work around breakage caused by some 2005-11-28 16:41:03 +11:00

Overview.

$ ./configure && make tests

You'll see some progress info. A failure will cause either the make to
abort or the driver script to report a "FATAL" failure.

The test consists of 2 parts. The first is the file-based tests which is
driven by the Makefile, and the second is a set of network or proxycommand
based tests, which are driven by a driver script (test-exec.sh) which is
called multiple times by the Makefile.

Failures in the first part will cause the Makefile to return an error.
Failures in the second part will print a "FATAL" message for the failed
test and continue.

OpenBSD has a system-wide regression test suite. OpenSSH Portable's test
suite is based on OpenBSD's with modifications.


Environment variables.

SUDO: path to sudo command, if desired. Note that some systems (notably
	systems using PAM) require sudo to execute some tests.
TEST_SSH_TRACE: set to "yes" for verbose output from tests 
TEST_SSH_QUIET: set to "yes" to suppress non-fatal output.
TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD
	SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER
OBJ: used by test scripts to access build dir.
TEST_SHELL: shell used for running the test scripts.
TEST_SSH_PORT: TCP port to be used for the listening tests.
TEST_SSH_SSH_CONFOTPS: Configuration directives to be added to ssh_config
	before running each test.
TEST_SSH_SSHD_CONFOTPS: Configuration directives to be added to sshd_config
	before running each test.


Individual tests.

You can run an individual test from the top-level Makefile, eg:
$ make tests LTESTS=agent-timeout

If you need to manipulate the environment more you can invoke test-exec.sh
directly if you set up the path to find the binaries under test and the
test scripts themselves, for example:

$ cd regress
$ PATH=`pwd`/..:$PATH:. TEST_SHELL=/bin/sh sh test-exec.sh `pwd` \
    agent-timeout.sh
ok agent timeout test


Files.

test-exec.sh: the main test driver. Sets environment, creates config files
and keys and runs the specified test.

At the time of writing, the individual tests are:
agent-timeout.sh:	agent timeout test
agent.sh:		simple agent test
broken-pipe.sh:		broken pipe test
connect-privsep.sh:	proxy connect with privsep
connect.sh:		simple connect
exit-status.sh:		remote exit status
forwarding.sh:		local and remote forwarding
keygen-change.sh:	change passphrase for key
keyscan.sh:		keyscan
proto-mismatch.sh:	protocol version mismatch
proto-version.sh:	sshd version with different protocol combinations
proxy-connect.sh:	proxy connect
sftp.sh:		basic sftp put/get
ssh-com-client.sh:	connect with ssh.com client
ssh-com-keygen.sh:	ssh.com key import
ssh-com-sftp.sh:	basic sftp put/get with ssh.com server
ssh-com.sh:		connect to ssh.com server
stderr-after-eof.sh:	stderr data after eof
stderr-data.sh:		stderr data transfer
transfer.sh:		transfer data
try-ciphers.sh:		try ciphers
yes-head.sh:		yes pipe head


Problems?

Run the failing test with shell tracing (-x) turned on:
$ PATH=`pwd`/..:$PATH:. sh -x test-exec.sh `pwd` agent-timeout.sh

Failed tests can be difficult to diagnose. Suggestions:
- run the individual test via ./test-exec.sh `pwd` [testname]
- set LogLevel to VERBOSE in test-exec.sh and enable syslogging of
  auth.debug (eg to /var/log/authlog).


Known Issues.

- If your build requires ssh-rand-helper regress tests will fail
  unless ssh-rand-helper is in pre-installed (the path to
  ssh-rand-helper is hard coded).

- Similarly, if you do not have "scp" in your system's $PATH then the
  multiplex scp tests will fail (since the system's shell startup scripts
  will determine where the shell started by sshd will look for scp).

- Recent GNU coreutils deprecate "head -[n]": this will cause the yes-head
  test to fail.  The old behaviour can be restored by setting (and
  exporting) _POSIX2_VERSION=199209 before running the tests.

$Id: README.regress,v 1.10 2005/10/03 10:14:18 dtucker Exp $