At 10:53 8-10-2002 +0200, Evilio del Rio wrote:
>Thanks for your comments. I have now setup a "t/" directory with two
>test scripts: 01-use.t which tests the usability of the module, and
>02-db.t which optionally tests the operabillity. Both use the Test::More
>module and the first is just tests the correct loading of all the
>modules needed:
>
>#!/usr/bin/perl
>
>use Test::More tests => 4;
>
>BEGIN { use_ok('CGI') }
>BEGIN { use_ok('DBI') }
>BEGIN { use_ok('DBIx::Browse') }
>BEGIN { use_ok('DBIx::Browse::CGI') }
>
>
>The other one begins with:
>
>#!/usr/bin/perl
>
>use Test::More tests => 17;
>
>SKIP: {
> skip("database tests (see README file on how to allow them)", 17)
> unless ( $ENV{DBIX_BROWSE_MAKE_TEST} && $ENV{DBI_DSN} );
>(...)
>
>So I still require some user intervention to allow all tests but now
>they are all standarized and separated (and explained in the README
>file).
>
>I think that this is exactly what you asked for. Please, could you tell
>me if it seems correct to you? I would like to be sure before releasing
>a new version.
Sounds great. Can't you run the tests when DBI_DSN is set, regardless
whether the DBIX_BROWSE_MAKE_TEST is set?
If you can, remove that environment variable? Let's make it as easy as
possible for the user.
Jeroen
