Current TAP diagnostics appear after the the test results in the standard TAP producers.
If one is capturing application output like stdout/stderr, the relevant output would appear before the test. I am often using the test for debugging and have some of my modules use Test::More's diag instead of print/log when running inside test scripts with verbose/debug turned on. That output always occurs before the test completes. Perhaps when a diagnostic message appears after a test, it could be numbered with the test it applies to if test numbering is on. And/or: Perhaps there needs to be more that just clean TAP, # diagnostics, maybe ! stderr for output classes. or Perhaps extreme programming is evil, and a test run should be just a test run. Failure assigns a bug to anyone remotely associated with the project, and they all have a big pow-wow to pass the hot potato of blame around. :) Disclaimer: I often operate outside of any boxes. I am often an edge case. In any given instance, I often don't know if I'm in or out, hump or tail. I offer ideas so that we can move the discussion from "Nobody would ever do that.", through "Why would you do that?" to "Well, I can't see how that is useful, but it's not too much trouble to allow it." That's what got me using Perl in the first place. -- Eric Hacker, CISSP aptronym (AP-troh-NIM) noun A name that is especially suited to the profession of its owner I _can_ leave well enough alone, but my criteria for well enough is pretty darn high.
