Slash Boxes
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 ]

chromatic (983)

  (email not shown publicly)

Blog Information [] Profile for chr0matic []

Journal of chromatic (983)

Monday May 30, 2005
04:23 PM

Making It Easier For Users to Report Test Failures

[ #24950 ]

Perl's module tools make it easy to bundle, distribute, and install software, most of the time. Other tools make it fairly easy to test software too. Of course, the tools for end-users lag somewhat behind the tools for developers, especially in places where developers are happy with their tools.

If you're a Perl-savvy developer and tests fail in a module you're installing, you know what your options are. Consider what a non-developer could do, though. Yet developers who ship their tests for end-users to run rely on receiving feedback about failures so that they can fix the code, the tests, the assumptions, or whatever's not right.

I've just released Module::Build::TestReporter which runs the tests as usual, hijacks their output, keeps a log of any failures and their diagnostics, and tells users what to do to report any failures to the developers. If you think this will solve a problem for you, give it a whirl. (I'd love to have feedback before I release it to the CPAN in a week or so.)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • One of the tough tasks for CPANPLUS at the moment is getting a reasonable hold of the test results from M::B. Because it works through the API, and not via a command call, results are lost, unless wrapped in an eval. This doesn't work if the tests passed and you still want to see the results. Is this going to enable successful results to be reported in verbose mode?

    I haven't had time to look at your module, but I certainly like the idea of a better test capture and reporting mechanism for M::B. CPANPLUS h

  • I agree the problem space seems worth addressing, and the docs and code looked reasonable to me at first pass.