comment on

I am much less worried about speed and more concerned with what a pain it is to write test modules with the current infrastructure due to its monolithic design.

In my naive world view, tests should emit TAP, test runners should manage test processes and collect the TAP, and test frameworks should tell the runners what to run and process the TAP and produce reports.

To that end I have been working on a TAP::Producer class for a while. Feel free to check it out and see if it serves your needs https://github.com/daotoad/TAP-Producer

TGI says moo

In reply to Re: the sorry state of Perl unit testing framework by TGI
in thread the sorry state of Perl unit testing framework by bulk88

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.


P is for Practical
	PerlMonks