App::Prove plugins, options, etc
Ovid
publiustemp-tapx at yahoo.com
Fri Oct 5 07:55:30 BST 2007
--- Eric Wilhelm <scratchcomputing at gmail.com> wrote:
> # from Andy Lester
> # on Thursday 04 October 2007 18:42:
>
> >Please. No more features, and let's abandon the extensibility until
>
> >3.1 if it means adding anything else.
>
> What exactly is the goal of 3.0 anyway?
To decouple the reading, parsing and interpretation of TAP so to make
it possible to do interesting things with testing. Note that I did NOT
say extensibility. I said "interesting things". Here's chromatic
doing interesting things with it:
http://www.oreillynet.com/onlamp/blog/2007/03/cpan_module_review_tapparser.html
http://tinyurl.com/24adgp
It's trivial to write a custom harness if need be. No, that's not
extending the current harness. That's replacing it. And guess what?
For the vast majority of users, what we have now is JUST FINE. If it's
not just fine, this means they're serious testers and therefore serious
programmers and therefore can figure out how to write their own
harness.
Push extensibility to 3.1. This doesn't hamstring our user base.
We're forgetting that the current code loses them *nothing* and still
gains them a hell of a lot they never had before. (By "nothing", I
accept that straps is something, but it has to go. And I reluctantly
agree that in-header TODO may need to be put bacK).
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Perl and CGI - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog - http://use.perl.org/~Ovid/journal/
More information about the tapx-dev
mailing list