RE: [Firebird-test] Catching up on postings

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

-----Original Message-----
From: 	Jason Chapman (JAC2) [mailto:ja...@ja...] 
Sent:	Monday, May 14, 2001 6:28 AM
To:	fir...@li...
Subject:	Re: [Firebird-test] Catching up on postings


<Snip>

> 3) All of the testing programs (including any script editors)
> should portable, to run on any platform which the engine runs on.
This may hamper development, I could work on some bits in Delphi for
Win32,
but that would under the "must be under all OS'" be a no-no.

<Sean>
Don't get me wrong, I'm one of Bill Gates drones, I know practically
nothing about C, C++ or *nux so I'd love to say that we should write the
testing programs in Delphi/Kylix.  However, the frank reality is that
the testing programs need to apply much more broadly.
</Sean>

> 4) Any choice of development tools (Delphi, C++, Python, Java or MS
> C# <big grin>) should carefully consider the overall expertise of the
> project members.
3 damages 4. Suddenly we've lost Delphi + MS anything.

<Sean>
Keep in mind that the testing programs are really designed (even TCS
today) as a command processor; taking in commands (scripts), executing
the commands and then reporting the results.  So, in the long run most
of the work in the testing process will be in the management/creation of
testing scenarios/scripts, which is something that everybody can make
very important contributions.

The testing programs themselves will probably require little maintenance
of their own, so the fact that most of us would really feel more
comfortable using Delphi which isn't cross-platform should really matter
in the long run - there will always be someone who can work on the
programs for us <grin>.

There, however, could be a role for Delphi in creating a nifty script
editor/manager, to save use from the depths/details of the XML (to use
David's example).
</Sean>