Test::Harness in Core

[David Golden]

On Mon, Jun 8, 2009 at 12:46 PM, Ovid<publiustemp-tapx at yahoo.com> wrote:
> What would it take for TH to be split into two distributions?  One of those would reside in core and only contain core features.  The other (Test::Harness::Extended?) would be where new features are developed.

Are you sure this isn't a job for roles?  ;-)  (j/k)

On the serious side, Test::Harness has done a pretty good job of
breaking up functionality into separate modules -- the problem is that
it's damn hard to replace any one of those in practice given the way
testing is called from EU::MM or M::B.  I recently added support for a
"HARNESS_SUBCLASS" environment variable so that TAP::Harness could
easily be replaced by TAP::Harness::Archive without re-writing
someone's build code.

That's a hack, but it's a symptom of the larger problem.  If
Test::Harness were written to make it easy to swap in components, then
that could the module that remains core and everything fancy could be
Test::HarnessX::Foo, etc.

-- David