Branislav Zahradník
Branislav Zahradník
Intended usage: there is a package providing REST resource with methods like `GET`, `POST`. Tests in project are organized by public api, for example `REST-resource-POST.t`. In this case it will...
hmm, ok, I got it ... so what about ``` my $coverdb = cover { ... }; test_coverage $coverdb, 'Foo::Bar::baz', statement ... ``` or ``` test_coverage { ... }, expect_statement_coverage...
problems with Test2 format: - it appends character to `reason` so to make it stream-parsable spec should prohibit tailing '{' in reason / directive description - for example: - which...
@exodist buffered subtest is an implementation ... does it matter when you read test output?
@exodist I have nothing against with buffering, that is good I just don't see any reason to say "this is buffered subtest output" (from parsing TAP later point of view)....
additional question: does anyone need to distinguish whether subtest was buffered or not ?
it makes difference when you are using non-console tools to process TAP Test2 can generate two plan rows in row which will make tools not supporting not-published-yet (and not-specified in...
``` # Subtest: foo ok 1 - foo { ok 1 1..1 } 1..1 ```
your example is ok, that braced subtest is not ... my original complain was that Test2 suite uses this braced, which is not supported by 3rd party TAP parsers. If...
As far as it looks like that root caused directly by `builtin::import` I'd suggest to experiment with source code finding combinations where behaviour is "very different from expected" or inconsistent...