Thu, Feb 02, 2006 at 03:26:26AM -0800, lothar.behrens@lollisoft.de napsal(a):
> > - it contains executable, and dir with text files
> > - each text file describe one test
>
> Sounds like a language to be defined first. If I would create a test
> suite, first I would
> find the smallest peaces of code to be implemented in a native language
> like C or C++.
I don't think so. We need to describe what we want. Then we could choose
the best suitable language for it. Maybe it is C or C++ or Perl or
whatever suite the developer.
> These peaces reflect typical or untypical usecases of the SQLXXX API.
>
> As I have some experience using plugins, I would suggest to implement
> these test
> peaces as plugins to be loaded by the name of the test.
It isn't easy to add new test (plugin). When we could describe each test
with text file (which could be automatically generated from mylog output)
we could easy add the new test to testsuite. So each new release has
no old bug. When we'll collect enough tests we have rock solid ODBC driver.
> To have more flexibility, I would define a language to get test data
> for it, but delegate
> the handling of the test to the plugin.
BTW we get the most flexibility by using ODBC API calls with parameters
obtained from mylog output. We cover all the situations this way.
I'm not sure now if I undestand you well. What do you mean with
"language to get test data"?
Regards,
Luf
P.S. I'm sorry if I misunderstand you.
