On Fri, Feb 25, 2005 at 10:22:33AM -0500, Joe Schaefer wrote:
> > More to the point is its completely unstructured output that comes not
> > as part of the test but between them.
>
> It might be worthwhile to associate that "unstructured output" with
> a particular test (either the previous "ok/not ok" line, or the
> following one). Right now I think Apache::Test puts its comments
> before the actual test output, which seems reasonable to me, but I'm
> not sure it's the norm.
Here's a common idiom where they come after:
ok( open(FILE, "foo") ) || diag $!;
> Is it possible to standardize this, so a generic harness knows
> which test a comment line acctually describes?
Of course its possible, but then they're no longer free form, unparsed
comments.
I'm going to call a big, fat YAGNI on this one for the time being. It
requires a change to both the protocol and testing libraries for a minimal
organizational improvement that really isn't much better than just looking
at the test output. And its all moot right now anyway as we don't even
have anything to gather and reformat the test output.
