Test::Harness in Core

[Andy Armstrong]

On 8 Jun 2009, at 21:38, Steve Purkis wrote:
> For example, I still think the App::Prove plugin system needs some  
> work (support plugin-defined cmdline params).  But arguably  
> App::Prove doesn't need to be in Core (ie: it wouldn't be used  
> directly by build scripts), so not something we need to worry about  
> here.

Yeah, the App::Prove plugin thing has never been fully resolved. And  
you're right that logically App::Prove feels like something that  
should live on its own but...

> As for adding Test::Harness to Core, I think it makes sense, but  
> only after we sort out the plugin / extension system.  Otherwise  
> we'll create a swath of backwards-compat pain that we've got to deal  
> with for years to come.


TH3 has been heading for core for a couple of years and will ship with  
5.10.1. I feel positive about that. The advantage of being in core is  
increased exposure, more feedback about what people want.

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! :)

-- 
Andy Armstrong, Hexten