On Sun, Dec 16, 2001 at 11:20:11PM -0700, chromatic wrote: > On Saturday 15 December 2001 11:44, Ilya Martynov wrote: > > > MGS> The two modules can already work together in the same script. So, if > > MGS> you have Test::Differences, which has superior complex data structure > > MGS> handling, why are you calling is_deeply() in the first place? > > > Still it is quite intersting idea to separate tests and results > > printing. Imaging that you can have pluggable output modules. So with > > one module you can have compact output with just ok/not ok, with > > another module you can build detailed report. > > Yeah, that's what I meant. The existing version works pretty well with > Test::Harness, but if someone (with GUI talent) wanted to write a nice Tk or > wx or GTK frontend, it'd be nice not to have to parse Test::Harness-style > results. > > That's really more of a Test::Builder style change, though. Worth > considering for the not-near future.
Its more of a Test::Harness::Straps thing, which is available now in the Test::Harness 2.00 alpha. Add GUI talent to taste. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One Lo, paste enema incarnation of the phrase anal retentive -- brevity
