With Test::Builder 0.80
$ perl -c ~/test/bang.t
/home/netbanx/test/bang.t syntax OK
$ cat ~/test/bang.t
#!perl
use Test::More tests=>1;
BEGIN {use_ok 'Fcntl', 'Pie'};
__END__
$ perl -c ~/test/bang.t
/home/netbanx/test/bang.t syntax OK
$ HARNESS_ACTIVE=1 perl -c ~/test/bang.t
Can't use an un
In article <[EMAIL PROTECTED]>, Nicholas Clark
<[EMAIL PROTECTED]> wrote:
> But it seems that this bug is only fixed as a side effect of that change, and
> it's not actually tested for. What's the best way to write a test that fits
> within the current frameworks to prevent any regression?
> It's
On Fri, Sep 19, 2008 at 03:35:36PM -0500, brian d foy wrote:
> In article <[EMAIL PROTECTED]>, Nicholas Clark
> <[EMAIL PROTECTED]> wrote:
>
> > But it seems that this bug is only fixed as a side effect of that change,
> > and
> > it's not actually tested for. What's the best way to write a test
2008/9/19 brian d foy <[EMAIL PROTECTED]>:
> In article <[EMAIL PROTECTED]>, Nicholas Clark
> <[EMAIL PROTECTED]> wrote:
>
>> But it seems that this bug is only fixed as a side effect of that change, and
>> it's not actually tested for. What's the best way to write a test that fits
>> within the cu
Fergal Daly wrote:
>> #!perl
>>
>> use Test::More tests=>1;
>> use Test::Builder::Tester;
>>
>> test_out('not ok 1 - use Fcntl;');
>> test_fail(+1);
>> use_ok 'Fcntl', 'Pie';
>> test_test( "Fails for bad export");
>> __END__
>>
>
> alternatively
>
> use Test::Tester;
> use Test::M
