Test::Harness in Core
xdaveg at gmail.com
Tue Jun 9 12:53:16 GMT 2009
On Tue, Jun 9, 2009 at 7:50 AM, Andy Armstrong<andy at hexten.net> wrote:
> On 8 Jun 2009, at 21:38, Steve Purkis wrote:
> I believe we can still sort out the plugin system without breaking
> backwards compatibility. App::Prove's public interface is pretty
> benign - I don't see anything there that'd have to be deprecated to
> support a better plugin interface.
> But certainly let's do it! :)
But please do it in Test::Harness. That's where you need the plugin
capability to let a simple Test::Harness live in core and let people
extend it in their own tests.
The fact that so much effort was put into App::Prove and not
Test::Harness is one reason why this problem still exists.
For example --- answer this quickly and without reading documentation:
which of the options to prove are supported by HARNESS_OPTIONS? Don't
know? Go look it up. Was there any well-thought-out reason for it?
Or just that no one bothered to keep the code in sync?
More information about the tapx-dev