On Fri, 2002-10-04 at 20:58, Jeroen Latour wrote:
>...
>
> Additional comments:
>
> Hello, Evilio Jose del Rio Silvan! Thanks for uploading your works to CPAN.
>
> Would it be too much to ask for a simple test script in the next
> release, so people can verify which platforms can successfully
> install them, as well as avoid regression bugs?
>
> A simple 't/use.t' that says:
>
> #!/usr/bin/env perl -w
> use strict;
> use Test;
> BEGIN { plan tests => 1 }
>
> use Your::Module::Here; ok(1);
> exit;
> __END__
>
> would be appreciated. If you are interested in making a more robust
> test suite, please see the Test::Simple, Test::More and Test::Tutorial
> manpages at <http://search.cpan.org/search?dist=Test-Simple>.
>
Hello Jeroen,
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.
Thanks again.
Cheers,
________________________________________________________________
Evilio Jose del Rio Silvan Centre Meditarrani d'Investigacions
[EMAIL PROTECTED] Marines i Ambientals
"Can music save your mortal soul?" - Don McLean
