2008/6/9 David Golden via RT <bug-Test-NoWarnings@rt.cpan.org>:
Show quoted text> Mon Jun 09 18:36:07 2008: Request 36603 was acted upon.
> Transaction: Ticket created by DAGOLDEN
> Queue: Test-NoWarnings
> Subject: Requires a plan even though Pod says otherwise
> Broken in: 0.084
> Severity: Normal
> Owner: Nobody
> Requestors: dagolden@cpan.org
> Status: new
> Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=36603 >
>
>
> Synopsis says I don't need to specify a plan, but an actual test
> suggests I do. (At least with the latest Test::More and Test::Harness
> that are strict about plans.)
Thanks.
The synopsis is ambiguous. It was written from the POV of adding
Test::NoWarnings to an already functioning test script. What I meant
is that if your script already specified "no_plan" then you can just
add use Test::NoWarnings without having to make any changes.
Test::NoWarnings was not intended to be the only Test::* module in a
test script. Of course there's no reason it couldn't be and so I'll
clarify the docs and maybe add an import but this is not high on my
list of things to do,
F
Show quoted text> You might also want to change import() to allow "use Test::NoWarnings
> tests => 1" as many other Test::* modules do. See Test::Exception as an
> example.
>
>
