RE: Are unittests expected to fail?

> 
> Hi folks,
> 
> I was going to submit a patch for something, but I thought 
> I'd give the unittests a blast and they failed. Or more 
> likely I failed to configure them correctly. I have never 
> tried using them before.
> 
> I then re-tried with a completely clean unmodified checkout 
> from CVS. Same result:
> - 2 failures out of 13 for TDS tests
> - 6 failures out of 20 for ODBC tests using UnixODBC.
> - 14 failures out of 20 for ODBC tests using iODBC.
> 
> So before I resort to debugging to find out if I've done 
> anything wrong, I'd like to know if this is known "normal" behaviour:
> - i.e. are the tests buggy/out-of-date/misleading and should 
> I just ignore these failures? 
> 
> Otherwise, are there detailed instructions for how to run the 
> unit tests anywhere?
>      - so far I've configured PWD.in
>      - granted suitable database rights to the user given in PWD.in
>      - run "make check" from the top level and also from
>         src/odbc.
> 
> In case this is abnormal behaviour, I have attached 2 files. 
> One is the 
> output from running the TDS tests. The other is the output 
> from the ODBC tests (when using unixODBC).
> 
> Anyone care to shed any light or got any ideas to help me
> fix my setup? Are there known gotchas?
> 
> Thanks a lot,
> 
> David
> 

You are using TDS 4.2. Try with an higher TDS version. Usually I try
with unixODBC. Current results (TDS5+, unixODBC) should be

- with GNU iconv + single-byte
 - TDS 0 fails
 - CTLib 1 fail (lang_ct_param using mssql, 0 under Sybase)
 - dblib 0 fail
 - ODBC 3 fails (type, transaction, putdata on mssql/another on Sybase)
- other iconv and/or multiple-byte (like UTF-8)
 - TDS 0 fails
 - CTLib 3 fails (t0009, lang_ct_param only using mssql, get_send_data)
 - dblib 2 fails (t0016, t0023 with core)
 - ODBC 4 fails (putdata, params, transaction, type)

I don't understand why 14 tests fail with iODBC....

freddy77