comment on

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.

-xdg

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.

In reply to Re^2: Become a CPAN Tester with CPAN::Reporter by xdg
in thread Become a CPAN Tester with CPAN::Reporter by xdg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks