Re^2: RFC: Perl Testing -- How to Introduce to a team

I've been wondering about that--in such a case, do you write a test For the bug (passes if it hits) or For the Solution to the bug? I'm thinking the former, and then just Reverse it when it's fixed (passes when the fixed code runs right.)

Thanks for the comment.
NovMonk

Comment on Re^2: RFC: Perl Testing -- How to Introduce to a team

Replies are listed 'Best First'.
Re^3: RFC: Perl Testing -- How to Introduce to a team by philcrow (Priest) on Oct 19, 2006 at 13:49 UTC
I write the test so it fails when the bug exists and keeps failing until I fix it. If you don't want it to show up for some period of time, mark it TODO. Phil	[reply]
Re^4: RFC: Perl Testing -- How to Introduce to a team by xdg (Monsignor) on Oct 19, 2006 at 15:36 UTC
I want to second this. It's very important to write a test that can replicate the bug before fixing it. -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply]


Syntactic Confectionery Delight
	PerlMonks