# from Ricardo SIGNES
# on Saturday 03 March 2007 07:11 pm:
>> use inc::testplan(0,
>> + 3 # use
>> + 199 # those others
>> );
>
>What is that ... for?
It's a substitute for
use Test::More (0 ? (no_plan) : (tests => 202));
... mostly because I don't like the number of parens in
A tangential comment:
The xUnit approach avoids this question of "counting" altogether -
you create one or more subroutines whose names begin with 'test',
each of which contain one or more assertions such as is_deeply($got,
$expected); and the test runner runs all the test* methods. It coun
* Eric Wilhelm <[EMAIL PROTECTED]> [2007-03-03T21:59:32]
> In fact, so much eyewringing that I've taken to this lately:
>
> use inc::testplan(0,
> + 3 # use
> + 199 # those others
> );
What is that ... for?
I often do this:
use Test::More;
my @test_data = load_data('t/whateve
On Mar 3, 2007, at 8:59 PM, Eric Wilhelm wrote:
Do you comment out the tests => foo and uncomment the no_plan line
whenever you edit tests, or do you use a ternary and the r0/r1 vim
idiom? Or do you just delete the 'tests' option and type no_plan
longhand?
I never use no_plan, except in the
# from Andy Lester
# on Saturday 03 March 2007 06:18 pm:
>Good Lord do I get frustrated at the handwringing over test
>counting. Look, it's simple. You write your tests. You run it
>through prove. You see how many tests it reports. You add it at the
> top of the file. Voila!
I'm not w
chromatic wrote:
> On Saturday 03 March 2007 18:18, Andy Lester wrote:
>
>> Good Lord do I get frustrated at the handwringing over test
>> counting. Look, it's simple. You write your tests. You run it
>> through prove. You see how many tests it reports. You add it at the
>> top of the f
On Saturday 03 March 2007 18:18, Andy Lester wrote:
> Good Lord do I get frustrated at the handwringing over test
> counting. Look, it's simple. You write your tests. You run it
> through prove. You see how many tests it reports. You add it at the
> top of the file. Voila!
But Andy, w
On Mar 3, 2007, at 8:15 PM, Eric Wilhelm wrote:
Yeah, you have to remember to put it at the end of the file, but it
may
be easier than counting tests.
Good Lord do I get frustrated at the handwringing over test
counting. Look, it's simple. You write your tests. You run it
through pro
At the bottom of a test file:
{my $finish = 1; END {$finish or die "\n unplanned exit"}};
Yeah, you have to remember to put it at the end of the file, but it may
be easier than counting tests. Thoughts? Maybe an 'until_done'
directive and 'tests_done' function? Ways to check that there is
* brian d foy <[EMAIL PROTECTED]> [2007-03-03T13:31:15]
> In article <[EMAIL PROTECTED]>, Ricardo
> SIGNES <[EMAIL PROTECTED]> wrote:
> > extensions:
> > CPAN::Reporter:
> > cc_author: 0
>
> I think in some cases this might work, but I can imagine options that
> I'd want, such as cc_au
In article <[EMAIL PROTECTED]>, Ricardo
SIGNES <[EMAIL PROTECTED]> wrote:
> * David Golden <[EMAIL PROTECTED]> [2007-02-28T22:39:01]
> > Is there a de facto standard for custom extensions to META.yml? (I
> > didn't see one in the spec.) An example might be fields beginning
> > with a capital let
11 matches
Mail list logo
