>>>>> On Sat, 15 Dec 2001 13:18:23 -0500, Michael G Schwern <[EMAIL PROTECTED]> said:
MGS> On Sat, Dec 15, 2001 at 10:52:07AM -0700, chromatic wrote: >> Wild idea: >> >> How about splitting out the error-reporting, with a nice default in >> Test::Builder or wherever, using optional modules if possible? >> >> use Test::More >> tests => 100, >> report => Test::Differences; 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. I have already something similar in unreleased version of new HTTP::WebTest. It supports various report plugins so test results can be represented in several ways. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Ilya Martynov (http://martynov.org/) TIV.net (http://tiv.net/) | | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
