Andy Lester wrote:
On Jun 19, 2007, at 10:52 AM, Mike Malony wrote:
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
expecte
On 6/19/07, chromatic <[EMAIL PROTECTED]> wrote:
On Tuesday 19 June 2007 14:06:05 Joshua ben Jore wrote:
> It's on CPAN with the original name. I just stole the namespace. I
> don't think chromatic will mind.
>
> It can even support the API described in Perl Hacks if or when it gets
> a custom i
On Tuesday 19 June 2007 14:06:05 Joshua ben Jore wrote:
> It's on CPAN with the original name. I just stole the namespace. I
> don't think chromatic will mind.
>
> It can even support the API described in Perl Hacks if or when it gets
> a custom import/unimport function.
Adding a custom import/un
On 6/19/07, Joshua ben Jore <[EMAIL PROTECTED]> wrote:
On 6/16/07, Joshua ben Jore <[EMAIL PROTECTED]> wrote:
> I took chromatic's Runops::Trace and hacked it up so I could do code
> coverage. I can now tell which code path is triggered by which inputs.
>
Ok, so now here's a new version. It's les
On Tuesday 19 June 2007, Mike Malony wrote:
> 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
On Jun 19, 2007, at 10:52 AM, Mike Malony wrote:
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 i
On 6/16/07, Joshua ben Jore <[EMAIL PROTECTED]> wrote:
I took chromatic's Runops::Trace and hacked it up so I could do code
coverage. I can now tell which code path is triggered by which inputs.
Check this badness out. The punchline is the lists of equivalent
inputs. Roughly. Ops can return diff
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
