Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jplindstrom (594)

jplindstrom
  (email not shown publicly)

Journal of jplindstrom (594)

Monday August 19, 2002
10:26 PM

Test more

[ #7187 ]

Test::More is cool.

I've done unit testing for one of my larger projects at work for some time now, but I did it all wrong. A bad first example of how to setup the test environment got me going in the wrong direction. Too much work for something that should be as simple as Test::More actually is. With Test::More I don't even need any of that.

Before, I thought it was a chore, adding tests after the fact. Using Test::More it's actually easier than not using it. Or at least the end result is a lot better for the same effort. It would actually work to do things XP.

Recently I looked at embedded tests, but it didn't seem simple enough to be worth it.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • My latest project uses Test::More, Test::MockObject, and Test::Exception. More domain-specific testing libraries based on Test::Builder! I'm hooked!

    • Pixie's test suite is starting to be heavily dependent on Test::Class. Now, if I could just get Test::Class to play a little more nicely with the debugger I'd be a happy man...