- (dtucker) [regress/README.regress] Add detail on how to run a single

test from the top-level Makefile.
This commit is contained in:
Darren Tucker 2004-06-18 14:14:43 +10:00
parent e826a8c9d9
commit 13fbe57722
2 changed files with 10 additions and 4 deletions

View File

@ -10,6 +10,8 @@
- djm@cvs.openbsd.org 2004/06/17 14:53:27
[regress/multiplex.sh]
shared connection env passing regress test
- (dtucker) [regress/README.regress] Add detail on how to run a single
test from the top-level Makefile.
20040617
- (dtucker) [regress/scp.sh] diff -N is not portable (but needed for some
@ -1283,4 +1285,4 @@
- (djm) Trim deprecated options from INSTALL. Mention UsePAM
- (djm) Fix quote handling in sftp; Patch from admorten AT umich.edu
$Id: ChangeLog,v 1.3407 2004/06/17 15:23:03 djm Exp $
$Id: ChangeLog,v 1.3408 2004/06/18 04:14:43 dtucker Exp $

View File

@ -32,8 +32,12 @@ TEST_SHELL: shell used for running the test scripts.
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:
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` \
@ -96,4 +100,4 @@ Known Issues.
unless ssh-rand-helper is in pre-installed (the path to
ssh-rand-helper is hard coded).
$Id: README.regress,v 1.5 2004/06/16 11:08:32 dtucker Exp $
$Id: README.regress,v 1.6 2004/06/18 04:14:43 dtucker Exp $