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 a team development, it may be handy to say "don’t worry about 
the plan, we'll keep it upto date, unless you tell us not too". 

The second bird is the one where we want to create a dashboard of testing 
results, and having the number of scripts helps with presenting a "script X of 
Y running" piece of information. Having a "test A of B in script X of Y" is 
nice to if you have a plan.

L 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 9 August 2006 5:06 AM
To: perl-qa@perl.org
Cc: Leif Eriksen
Subject: Re: Idea for updating the plan

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::Harness(? - I could be wrong) 
> update the plan in the scripts it just ran.

Why bother?  If you're going to assume that the number of tests is correct 
without looking at it, why do you need a plan anyway?

I really don't understand this.  People say "Oh, keeping the test count up to 
date is difficult!  I don't want to count all of the tests myself by hand!"

I have a vim macro to toggle the counter between 'no_plan' and a number.  I run 
the tests with perl -I or perl -Mblib, eyeball the output, then when I've 
finished the feature and want to check it in, I update the test count.

This has *never* been a burden for me and it has saved me from checking in 
broken code several times.

Do I work very differently from everyone else?

-- c

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.7/411 - Release Date: 7/08/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.7/411 - Release Date: 7/08/2006
 
**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are addressed.  If
you received this e-mail in error, please notify the HPA Postmaster, [EMAIL 
PROTECTED],
then delete  the e-mail.
This footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services. For more
information about use, disclosure and access see our Privacy Policy at
www.hpa.com.au
**********************************************************************

Reply via email to