I have even heard a prominent CPAN contributor say that testers reports without verbose output are useless
I'm a little surprised by this comment. Tests reports, even without verbosity, include the details of failing tests, such as its label, line number, and any diagnostic output.
My own experience developing CPAN::Reporter and other modules is that almost any test report is helpful. The exceptions have been some issues with CPANPLUS where no details are provided, which I think had to do with Module::Build support. (I don't know if that has been addressed, and frankly, now that CPAN.pm supports Module::Build and does test reporting, I've stopped paying attention to CPANPLUS.)
Nevertheless, verbose reporting is an interesting idea and I'll put it on the Todo list to add as a configuration option.
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||