Andy Armstrong wrote:
> That looks pretty usable. I wonder if it might be better to package
> those YAMLish annotations as a special kind of diagnostic
>
> # Normal diagnostic
> ## got: 1
> ## expected: 0
Please read the bottom of this page.
http://perl-qa.yi.org/index.php/TAP_Proposals
> That
On 9 Mar 2007, at 21:57, Michael G Schwern wrote:
http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax
There's already a proposal for this which nobody's found serious
fault with.
Its, oh, 9 months old now. Its backwards compatible with existing
TAP. It
both solves the problems of associ
http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax
There's already a proposal for this which nobody's found serious fault with.
Its, oh, 9 months old now. Its backwards compatible with existing TAP. It
both solves the problems of associating diagnostics with a specific test and
making them m
On 3/9/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 9 Mar 2007, at 16:15, Eric Hacker wrote:
> I know. It probably isn't hard for a human to figure it out. A TAP
> consumer can only really make a best guess though.
It wouldn't be hard to information to the TAP to associate
diagnostics with t
On 3/9/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 9 Mar 2007, at 13:37, Eric Hacker wrote:
> Current TAP diagnostics appear after the the test results in the
> standard TAP producers.
D'you mean messages produced with diag() ? They appear in same order
relative to the test results in the T
On 9 Mar 2007, at 16:15, Eric Hacker wrote:
I know. It probably isn't hard for a human to figure it out. A TAP
consumer can only really make a best guess though.
It wouldn't be hard to information to the TAP to associate
diagnostics with tests but where would that information come from?
Cur
On 9 Mar 2007, at 13:37, Eric Hacker wrote:
Current TAP diagnostics appear after the the test results in the
standard TAP producers.
D'you mean messages produced with diag() ? They appear in same order
relative to the test results in the TAP as they do in the test.
Disclaimer: I often oper
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 o
