Re: [Firebird-test] Testing FB1

[John B. <bel...@cs...>]

On Thursday, August 2, 2001, at 09:49 PM, Mark O'Donohue wrote:

> John Bellardo wrote:
>
>>
>> Yup, changes in error message text, removing the extra space in number 
>> converted into strings, and the like.
>
> Yep, go ahead, ocmmit them
>
> Im keen to experiment with dejagnu for limit, (working on a rough 
> framework as we speak) and if we decide it's a good idea, will try for 
> some sort of extract script to parse the "$CREATE" etc out of the TCS 
> files.

I'm interested in seeing how well it works out too.

>
> An alternative track that also deserves consideration, is (as Sean 
> points out) adjusting the TCS test tool parser to run from text files.

The hardest part will be handling the test hierarchy that TCS has.  
There are global tests, platform tests...

>
> Long term dejagnu/expect offers a much richer control language for 
> driving test cases and checking results.  And I think in writing a new 
> test tool, (other than something for a thrasher) we would end up with 
> the same problems as the current TCS program.
> Anyway dejagnu  does run on all our platforms (including win32).

If we choose to go with dejagnu we could still take advantage of a flat 
file modified TCS.  We could make an expect script front end for all 
tests still run under TCS, and still use dejagnu to drive the whole 
thing until we have moved all tests out of TCS control.  From what I 
have seen so far that should be fairly simple to set up given a slightly 
modified TCS.

>
> So I'd like to use it to test limit, to see how we go with it.
>
>
> BTW: I can't remember if I said, but I commited Franks TCS database 
> extract tools into the TCS tree, and added a few simple instructions 
> and script into TCS on how to build TCS.


-John