On Sat, Sep 24, 2011 at 04:34:12PM -0600, Karl Williamson wrote: > I do a 'make test_harness' for my local testing. I'm having trouble > grokking why harness would allow incorrect TAP output, and TEST > wouldn't; nor is it documented AFAICT. Is there a reason for this > besides tuitlessness? I would have thought the two things would try > hard to have consistent pass/fail results; leaving only weird cases > where they would differ. I *think* that TEST is actually stricter than harness. I don't know if it's possible to ask Test::Harness to be stricter in its parsing of TAP. [I guess therefore that yes, it's tuitlessness]. I think that having t/harness be as strict as possible would be beneficial, at least for development versions. Nicholas ClarkThread Previous | Thread Next