From: Michael G Schwern schw...@pobox.com
I think we don't have to guess at that. Structured diagnostics are only
associated with test results (and possibly start/end of test info). They're
not used like diag() is now as both a warning mechanism and a test
I may have missed the point here, but would it be sufficient to have
two flavours of diagnostic calls, distinguishing between pre-test
diagnostics (`forewarn()`) and post-test diagnostics (`reflect()`), or
is the problem that ok() must be a single function call?
If that's possible, maybe we can
On 2012.7.11 2:39 PM, Daniel Perrett wrote:
I may have missed the point here, but would it be sufficient to have
two flavours of diagnostic calls, distinguishing between pre-test
diagnostics (`forewarn()`) and post-test diagnostics (`reflect()`), or
is the problem that ok() must be a single
On 2012.6.1 5:40 AM, Steffen Schwigon wrote:
I am about to upload Test::TAPv13. I also did an prepan entry for that.
PrePAN: http://prepan.org/module/429En4oFbn .
URL: https://github.com/renormalist/Test-TAPv13
Synopsis:
use Test::TAPv13 ':all'; # must come before Test::More
Hi!
I am about to upload Test::TAPv13. I also did an prepan entry for that.
PrePAN: http://prepan.org/module/429En4oFbn .
URL: https://github.com/renormalist/Test-TAPv13
Synopsis:
use Test::TAPv13 ':all'; # must come before Test::More
use Test::More tests = 2;
my $data = {
