- Original Message
From: Ovid <[EMAIL PROTECTED]>
I get very tired of correcting my own emails. One day I'll learn :)
> I have two minor point, neither of which is all that serious.
"points"
> foreach my $foo ( $object->foo ) {
>ok looks_like_number($object->$foo),
> "... a
On 8 Aug 2006, at 04:58, A. Pagaltzis wrote:
* Daniel Risse <[EMAIL PROTECTED]> [2006-08-08 05:10]:
So something like this:
use Test::Simple 'no_plan';
use Test::Terminated;
# insert tests here
# signal we made it to the end okay
terminated_ok();
It occurs to me that you don’t even need t
Following in the footsteps of the recent discussion on extending no_plan
to cover the case of us making sure the script actually finished
'normally', it occurred to me that another thing that might be useful is
a means to have Test::Harness(? - I could be wrong) update the plan in
the scripts it ju
On Tuesday 08 August 2006 00:27, Adrian Howard wrote:
> Did we ever figure out if T::H not doing this was a bug or a feature?
I vote bug.
-- c
On Tuesday 08 August 2006 00:30, [EMAIL PROTECTED] wrote:
> Following in the footsteps of the recent discussion on extending no_plan
> to cover the case of us making sure the script actually finished
> 'normally', it occurred to me that another thing that might be useful is
> a means to have Test:
* Ovid <[EMAIL PROTECTED]> [2006-08-08 08:55]:
> Without the test plan, the bottom bar is merely red or green.
Making no argument about the test plan, I would say that this is
how it should be anyway. You’re either passing your tests or you
aren’t. If not, then the number of failures is of interes
* chromatic <[EMAIL PROTECTED]> [2006-08-08 21:10]:
> I have a vim macro to toggle the counter between 'no_plan' and
> a number.
There are also tricks in laying out your test code to make this
easier, like the one I showed recently where you increment the
plan count piecemeal throughout the file i
I'm trying to kill two birds with one stone here.
The first, bring the plans upto date, is probably most useful in the bulk
update case, or where there are a number of developers creating, updating and
testing code. For a single developer minding their own stuff, its probably
overkill, but for
chromatic wrote:
I have a vim macro to toggle the counter between 'no_plan' and a number.
Could you share that with us? (Adding to new macros to .vimrc is where
I'm *really* Lazy.)
Thanks.
jimk
On Tuesday 08 August 2006 18:53, James E Keenan wrote:
> chromatic wrote:
> > I have a vim macro to toggle the counter between 'no_plan' and a number.
>
> Could you share that with us? (Adding to new macros to .vimrc is where
> I'm *really* Lazy.)
map ,ton :%s/More tests =>/More 'no_plan
* chromatic <[EMAIL PROTECTED]> [2006-08-09 04:05]:
> map ,ton :%s/More tests =>/More 'no_plan'; # tests =>/
> map ,toff :%s/More 'no_plan'; # /More /$b
map ,ton :%s/More \zs\zetests =>/'no_plan'; # /
map ,toff :%s/More \zs'no_plan'; # //$b
Still trying to come up with a JAVH,
--
James E Keenan wrote:
Could you share that with us? (Adding to new macros to .vimrc is where
I'm *really* Lazy.)
I only know enough vim programming to be dangerous, but:
",v" brings up my .vimrc
",V" reloads it -- making all changes active (have to save first)
map ,v :sp $VIMRC_
map ,V :sou
I've just uploaded CPAN::Reporter to CPAN and it should soon be
available on mirrors worldwide.
As part of my goal of improving the availability of test information for
Vanilla Perl, I decided to try to get Test::Reporter working with CPAN
rather than CPANPLUS. The result is CPAN::Reporter, th
13 matches
Mail list logo
