On 7 February 2010 08:45, Ovid <[email protected]> wrote:
> I would love feedback (via actual use) of a development version of Test::Most
> available at http://search.cpan.org/~ovid/Test-Most-0.21_04/. If you're not
> familar with it, instead of this:
>
> use strict;
> use warnings;
> use Test::Exception 0.29;
> use Test::Differences 0.500;
> use Test::Deep 0.106;
> use Test::Warn 0.11;
> use Test::More 0.94;
> use Test::More tests => 42;
>
> You type:
>
> use Test::Most tests => 42;
>
>
> Yes, we have strict and warnings enabled by default (this is a devel version
> only and if it's causing serious pain, I might pull it).
>
> Note the version numbers. I went through through those various test modules
> and saw how many fixes and upgrades there were. As a result, I realized that
> if I give people a big steaming pile of ones and zeroes, they might get
> frustrated to have to upgrade all of those modules individually. So
> Test::Most is now "one stop shopping". I hope to periodically release it when
> the modules it depends on are upgraded.
>
> Also, some test modules are problematic. For example:
>
> use Moose;
> use Test::Deep;
>
> That gives you a prototype mismatch warning. So you can omit underlying
> modules if needed:
This is caused by both modules exporting a blessed function by default
and Moose's one sets a prototype.
More generally, it would be nice if any module importing module had a
way to control the exports of those modules.
use Test::Most imports => { Test::Deep => [ foo, bar ], Test::Simple => [buz]}
I was going to suggest that it skip any module that has already been
imported, that way you could do
use Test::Deep qw(foo bar);
use Test::Simple qw(buz);
use Test::Most;
but I can't think of a way to detect that,
F
> use Test::Most tests => 42, '-Test::Deep';
>
>
> (I'll provide a fix for the Moose/Test::Deep nit in a later release).
>
> Side note: I believe the Test::Class::Most failures are resolved. After
> David Cantrell gave me access to a server its build failed on, I found some
> serious issues that forced me to rethink the module. "use feature" and "mro"
> were pulled entirely.
>
> Cheers,
> Ovid--
> Buy the book - http://www.oreilly.com/catalog/perlhks/
> Tech blog - http://use.perl.org/~Ovid/journal/
> Twitter - http://twitter.com/OvidPerl
> Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
>
>
>
