On 15/01/2008, Ovid <[EMAIL PROTECTED]> wrote:
> Test::Harness used to be very limited. We couldn't do a lot with it,
> but when we started testing, most of us didn't do a lot with it. As we
> understood more about testing, we understood better many things we
> wanted. As a result, Schwern poste
On 15 Jan 2008, at 11:18, Ovid wrote:
[snip]
* Make it subclassable.
* Allowed deferred plans.
* Allow for TAP upgrades (YAMLish, YAMLish, YAMLish!).
* "On Fail" callbacks? (I realize lots of people will squawk here)
* [insert your desired features here]
Don't get hung up on the "On
Ovid wrote:
Test::Harness used to be very limited. We couldn't do a lot with it,
but when we started testing, most of us didn't do a lot with it. As we
understood more about testing, we understood better many things we
wanted. As a result, Schwern posted a great plan for rewriting
Test::Harnes
On Tuesday 15 January 2008 03:18:11 Ovid wrote:
> Now we're starting to see more and more limitations with Test::Builder.
> I don't want this to come across as bashing chromatic or Schwern, the
> two people who've done most of the great work in writing this and
> related code. They produced a gr
Test::Harness used to be very limited. We couldn't do a lot with it,
but when we started testing, most of us didn't do a lot with it. As we
understood more about testing, we understood better many things we
wanted. As a result, Schwern posted a great plan for rewriting
Test::Harness. It worked