FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

will trillich wrote:
> when we run "make check" we get lots of output, but it
> it not affected at all by the PWD file (we use genuine
> credentials and then randomized credentials and save
> "make check > outputlog" and "diff" shows NO difference
> between the two). either way "11 of 15 tests failed"...
> 
> boy there's a lot of output! are any of these actual
> connect errors? if not, how can we test the db server
> connection?

$ build/src/dblib/unittests/t0001 -h
t0001: unknown option -- h
usage:  t0001 
        [-U username] [-P password]
        [-S servername] [-D database]
        [-i input filename] [-o output filename] [-e error filename]

All db-lib unit tests accept command-line arguments.  If none is provided
(as in the case of "make check"), the PWD file is consulted.  Some of the
db-lib unit tests also report the location fo the PWD file that was read. 
It should be in the parent of the src directory.  

In case it's not clear: the SRV line in PWD refers to a server in
freetds.conf.  If your freetds.conf isn't right or isn't in the right
place, your unit tests won't work.  

tsql can also be used and can bypass freetds.conf.  See "man tsql".  :-)

> make[5]: Entering directory 
> `/dump/freetds-0.64.dev.20050905/src/tds/unittests'
> t0001.c: Testing login, logout
> tds_connect() failed
> try_tds_login() failed
> FAIL: t0001

Yes, that's a connect error.  All your tests should pass.  Connecting
successfully has been known to make a big difference.  ;-)

HTH.

--jkl