comment on

It isn't a case of what I'm doing, it's what they do--and the reason I don't use them!

XX.X% passed is not the only information you get out of a T::B based test suite. It's certainly not the information I'm focused on when I'm developing.

All I'm looking for is whether the last test I wrote passed or failed. Personally I find that the existing tools give me this info pretty easily. Especially now that Test::Builder displays the test description so that it can be read without dropping into verbose mode.

The only place I find this information more tricky to find, sad to say, is with my own Test::Class - and I'm working on fixing that :-)

This isn't to say the pretty numbers and statistical summaries are completely useless. While it's not of much relevance during development, it can be a useful diagnostic tool at install/distribution time.

In reply to Re^7: Self Testing Modules by adrianh
in thread Self Testing Modules by Sheol

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.


Do you know where your variables are?
	PerlMonks