On 21 Jan 2007, at 09:07, Ovid wrote:
I suspect what Andy was meaning was that it's OK to break the
underbelly of Straps, Point, etc., and not the actual Test::Harness
API, since it's the former I was referring to.
TAPx::Harness::Compatible is still intended to pass all of the
Test::Harness tests. However, I'm not sure what to do about darkpan
reliance on things they shouldn't be relying on. The current testing
framework is simply too limited and most acknowledge that something
new
needs to come along. However, it's going to be awfully tough to come
up with something new if we don't change *something*. I'm just
worried
about what it is we can safely change.
I have a CPAN mirror that I'm planning to grep in it's entirety
looking for evidence of dependencies on Test::Harness::Straps|Point|
whatever.
My current plan for Test/Harness.pm itself is to keep the API the
same but printed (and possibly captured) output will be coming from
TAPx::Harness - so anything that relies on that will likely break.
--
Andy Armstrong, hexten.net
