freebsd-nq/crypto/openssh/regress
2004-01-07 11:10:17 +00:00
..
agent-getpeereid.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
agent-ptrace.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
agent-timeout.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
agent.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
authorized_keys_root Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
broken-pipe.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
bsd.regress.mk Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
connect-privsep.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
connect.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
copy.1 Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
copy.2 Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
dsa_ssh2.prv Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
dsa_ssh2.pub Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
dynamic-forward.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
exit-status.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
forwarding.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
keygen-change.sh Vendor import of OpenSSH-portable 3.6.1p1. 2003-04-23 16:53:02 +00:00
keyscan.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
Makefile Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
proto-mismatch.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
proto-version.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
proxy-connect.sh Vendor import of OpenSSH-portable 3.6.1p1. 2003-04-23 16:53:02 +00:00
README.regress Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
reconfigure.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
rekey.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
rsa_openssh.prv Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
rsa_openssh.pub Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
rsa_ssh2.prv Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
runtests.sh Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
sftp-badcmds.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
sftp-batch.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
sftp-cmds.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
sftp.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
ssh-com-client.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
ssh-com-keygen.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
ssh-com-sftp.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
ssh-com.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
stderr-after-eof.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
stderr-data.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
t4.ok Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
t5.ok Vendor import of OpenSSH 3.3p1. 2002-06-27 22:31:32 +00:00
test-exec.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
transfer.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
try-ciphers.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00:00
yes-head.sh Vendor import of OpenSSH 3.7.1p2. 2004-01-07 11:10:17 +00: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 yo "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.


Individual tests.

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:. 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.


$Id: README.regress,v 1.1 2003/09/04 05:39:54 dtucker Exp $