RE: [Firebird-test] Catching up on postings

[Leyne, S. <sl...@at...>]

David,

-----Original Message-----
From: 	David Jencks [mailto:dav...@ea...] 
Sent:	Monday, May 14, 2001 1:26 AM
To:	fir...@li...
Subject:	Re: [Firebird-test] Catching up on postings

Hi,

Well, yes, I already started talking about it.

<Sean>
I didn't mean to imply that you hadn't.  I just wanted to re-focus the
discussion to a higher level before we got immersed in the almost
inevitable "religious" wars regarding C++ vs. Java vs. Python...

"Talking about the tools before we have defined the problem is like
putting the cart before the horse."
</Sean>


I have nearly completed a java scripting/testing solution based on xml
script/test files.  It can include the results of db access in the xml
file, and compare the current results with a stored reference.  Being
written in java, it will be easy to extend to test parallel db access.

<Sean>
That's great news! 

I'm wondering though, why did you choose XML as the file format, as
compared to straight text?
</Sean>

 
Obviously it is best adapted to testing via jdbc drivers, 

<Sean>
Have you looked at the Sun JDBC compliance testing routines?
</Sean>

but I think it might be worthwile investigating how hard it would be to
write adapters to
use odbc drivers, IBO, and possibly generating dynamic and static sql c
or
c++ programs.  

<Sean>
Personally, I'd like to leave the issue of IBO and dynamic/static C or
C++ programs to a much, much later time.  We have enough on our plate.
</Sean>

I think having a single cross platform execution engine would be rather
desirable.  

<Sean>
Agreed!
</Sean>

I don't think reliance on isql is appropriate.

<Sean>
Before Ann has a chance to ask, why not?  

ISQL needs to be tested, so why not use it as part of the tests?
</Sean>



Translating the TCS tests to any other format is going to be a large
amount
of work.  Its easy enough to dump say each test into an xml file, but
extracting the sql and expected results into a more reasonable format
will
be time consuming.  The NIST tests look only slightly easier to move to
a
different system than TCS.

<Sean>
Don't understand what you mean about extracting the SQL?
</Sean>

Would a provisional dtd for what I am working on and sample document be
helpful? Both are subject to change by me before I show the code, but
should give an idea of what I'm after.

<Sean>
Personally, I'd like to talk about general approach before diving into
the details.
</Sean>