FreeTDS Development Group

["Thompson, Bill D (London)" <bill_d_thompson AT ml.com>]

Just FYI

I'm also testing.
the tds unittest "flags" just works for SYBASE servers (TDS 4.2 or 5.0) 
I've got a patch to make it work for SQL server servers too...(which will
come with my other patches, but is :

    /* check select of 2 field */
    test_begin("select c, b from #tmp1 for browse");
    info = tds->curr_resinfo;

    if (IS_TDS7_PLUS(tds)) {
        if (info->num_cols != 2)
            fatal_error("wrong number or columns returned");
    } else {
        if (info->num_cols != 3)
            fatal_error("wrong number or columns returned");
    }

Your other failure is on the "dynamic1" test program. This works for me on
all TDS versions.

Bill

> -----Original Message-----
> From: David Fraser [SMTP:david AT abelon.com]
> Sent: 22 October 2003 13:00
> To:   FreeTDS Development Group
> Subject:      [freetds] 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
> 
> --
> David Fraser, Consultant, Abelon Systems Ltd, UK
> http://www.abelon.com << File: checktds.txt >>  << File: checkodbc.txt >>
> << File: ATT2169635.txt >>