FYI, at the drizzle Birds of a Feather session last night, it was
decided that a test suite which outputs TAP is the best solution. You
will see Andy and others (Ronald, Giuseppe, etc) begin to expand on the
discussion last night. :)
Cheers, and good to see you here Mats!
-jay
Mats Kindahl wrote:
> Hi!
>
> I noted that there is a blueprint for refactoring the tests. I would
> suggesting replacing it with something entirely different: a TAP based
> test system. I have been spending some spare time on writing a simple
> module for writing tests for the MySQL server using Perl and the Test
> modules. Essentially, this would make the tests be Perl scripts that can
> be checked using 'prove'. Other languages are of course possible to use,
> since the TAP protocol is a generic test protocol (used by at least Perl
> and PHP, AFAIK).
>
> In addition to providing a full "test language" in the form of a
> scripting language (Perl in my case), it removes diff-based testing,
> which has proven to be very shaky in terms of needing constant "test
> result updates". For TAP-based tests, the tests themselves check the
> result and just provide "ok" or "not ok".
>
> Basically, it would make tests look something like this (syntactic
> details are still evolving):
>
> use Test::More tests => 1;
> use Test::Drizzle {
> <options for servers>
> };
>
> my $client = new Test::Drizzle::Client;
>
> connection $client;
> sql "CREATE TABLE t1 (a INT)";
> my $result = sql "SHOW TABLES";
> ok($result->contain("t1"));
>
> Just my few cents,
> Mats Kindahl
>
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to : [email protected]
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
