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 ]

2shortplanks (968)

2shortplanks
  (email not shown publicly)
http://2shortplanks.com/
AOL IM: trelane2sp (Add Buddy, Send Message)
Yahoo! ID: trelane2sp (Add User, Send Message)

Mark Fowler has never been the same since he was elected leader of the London Perl Mongers. The strain manifests itself mainly in releasing various [cpan.org] modules [cpan.org] to CPAN, giving talks [2shortplanks.com], and use of the Trelane nick on #london.pm for endless procrastination. Doctors are still seeking a cure.
Thursday July 01, 2004
11:34 AM

Test::Builder::Tester release, Test::DatabaseRow to come..

[ #19628 ]
I just released a new version of the test suite module testing module Test::Builder::Tester. We've been using it for a few weeks at Fotango and we haven't had any problems with it, so I thought it was about time I released it to the masses (so they can point out all the things I've forgotten to do in this release ;-) )

This version now allows you to ignore if the error output doesn't match what you've declared when you're checking the output of your test suite's test. This is most useful when you're developing stuff (I've been using it while I've been building the new version of Test::DatabaseRow) and you're not entirely sure what format the debug output's gonna take, and you don't want to write those tests just then.

The new version of Test::DatabaseRow's in my subversion repository. It has loads of new features - testing that all rows match a criteria, specifying criteria based on what a row contains, checking that rows come out in the right order... I think it all works now apart from the debug output - which is of course one of the most important things with a Testing tool - it has to help you fix the bugs once you've found them.

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.