On 8/2/07, Scott McWhirter <[EMAIL PROTECTED]> wrote:
>
> On 8/2/07, nadim khemir <[EMAIL PROTECTED]> wrote:
> > On Tuesday 19 June 2007 17:52, Mike Malony wrote:
> > > So I'm working my project, and I've got one other more junior coder
> with
>
So I'm working my project, and I've got one other more junior coder with
me.
Has anyone tried writing test files as part of their spec's?
An overview document would also be needed, and some time walking through the
expected testing. But it sure would be setting clear expectations.
Comments?
M
Short answer - Aha! It is something on my machine at work, that old 5.6 and
such. I got it working on another machine. Thanks all.
Longer answer -
so I figured maybe something is wrong with my installs. So, hopped to this
darling work laptop, from which I am now typing.
Flushed the old 5.6 A
So, despite some fine advice. I'm not able to collect stats on my own .t
files.
I have some questions here, and I'll be posting more later.
Thanks for all the help
On 2/2/07, Paul Johnson <[EMAIL PROTECTED]> wrote:
On Fri, Feb 02, 2007 at 01:32:37PM -0600, Mike Malo
I'm into testing, got some nice .t files, and prove tells me things I'd
rather not hear. So, my next step on the straight and narrow path of
testing, is to gauge my testing coverage.
IN the doc, the synopsis suggests
"perl -MDevel::Cover yourprog args
cover"
But what can you use in 'yourpro
