Adam Kennedy wrote: >> I propose that we prefix lines from STDERR with '! ' in the same way >> that '# ' is used for diagnostics. wstat and exit can just be >> >> wstat 256 >> exit 1 > > The problem with STDERR and exit is that we can't actually use them for > anything significant. > > Otherwise when dealing with TAP streams that don't have a concept of an > exit code or a seperate error channel, the most common example being web > testing, we're left high and dry. > > That's always been the main reason to intentionally ignore the exit code > at least.
Am I TALKING TO MYSELF?! We do *not* have to decide on a fixed set of diagnostics you attach at the end of a test! We can allow the wait status, the exit status, the HTTP status... whatever you like. Put them in as you need. http://www.nntp.perl.org/group/perl.qa/2007/03/msg8155.html Extensibility is the key. This is why I like a YAML or JSON format so much. We can always add to it. http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax 1..2 ok 1 ok 2 done (or whatever we wind up using for "end of tests") --- exit status: 23 wait status: 0 http status: 404 human readable status: Yer screwed. psychological status: I'm feeling fine, thanks ... We can leverage any existing status system we want. HTTP status. Exit status. Throw them all in! Don't find TAP's existing statuses rich enough? Add your own extension keys! A particular status code not make sense for your application? Leave it out!
