Re: Using debugger breakpoints in Test::Class code

in reply to Using debugger breakpoints in Test::Class code

Gerard Meszaros wrote a wonderful book on refactoring tests - xUnit Test Patterns (amazon link)
He lists code smells:

Eager Test (testing too much at once)
Conditional Test Code (he suggests limiting the use of "if" in tests)
Obscure Test (what is being tested?)
Test Code Duplication

At $work I cleaned up our test suite just a bit, removing eager tests, conditional logic and obscure tests. I haven't use Test::Class.
Meszaros says test could should be drop dead simple.

Comment on Re: Using debugger breakpoints in Test::Class code

Replies are listed 'Best First'.
Re^2: Using debugger breakpoints in Test::Class code by secondturtle (Initiate) on Nov 19, 2008 at 19:35 UTC
Funny that you would cite a book about xUnit testing in an attempt to support your suggestion that I shouldn't be using the most widely adopted perl implementation of xUnit. I haven't read Meszaros's book (yet), but it sounds like he knows what he's talking about. Thanks for the suggestion.	[reply]

In Section Seekers of Perl Wisdom