On Wed, Dec 12, 2001 at 04:38:20PM -0500, Barrie Slaymaker wrote: > I've written a Test::Differences[1] that outputs things like: > > not ok 5 > # Failed test 5 in blib/lib/Test/Differences.pm at line 221 fail #4 *TODO* > # +-----+----------+ > # | Got | Expected | > # +-----+----------+ > # | a\n | a\n | > # >xxxxx* b\n < > # | c\n | c\n | > # >xxxxx* d\n < > # | e\n | e\n | > # +-----+----------+ > > when passed strings, arrays of strings, arrays of hashes, or arrays of > arrays of strings (basically, all the result types DBI's fetchall_...() > methods can return plus whole strings).
Oooooooh, pretty. Beats the hell out of is_deeply. Mind if I steal it? :) > I would like to make Test::Differences autodetect Test::More and others > like it so it can extend them "seamlessly" like so: In that case base yourself on Test::Builder and it should all Just Work. > Feedback on the module itself is welcome, but I also want to know what > the preferred way to mix in to Test::Straps supported environments is, I don't follow. You mean Test::Harness::Straps? > and if there's an equivalent way to "mix in" with Test.pm. You can use unpublished bits like $Test::ntest. It should be safe since Test.pm is stable (ie. dead). -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One I SEE A RED ASS AND I WANT TO PASTE IT BLACK WON'T OPEN ANYMORE I PASTED UP THE CRACK -- swansong
