* Chad Granum [2016-12-13T11:35:19]
> ok, thanks for trying that, I will look into it when I have time and if
> nothing else at least explain why it behaves like it does. If it is a bug I
> will fix it.
This has remained a problem for me, so this morning I had a run through it, and
I still think
ok, thanks for trying that, I will look into it when I have time and if
nothing else at least explain why it behaves like it does. If it is a bug I
will fix it.
On Tue, Dec 13, 2016 at 8:18 AM, Ricardo Signes
wrote:
> * Chad Granum [2016-12-13T11:13:56]
> > I would like to see the results when
* Chad Granum [2016-12-13T11:13:56]
> I would like to see the results when you use
> Test2::Tools::Subtest::subtest_streamed() which is the actual equivalent to
> Test::More::subtest().
Thanks for the pointer. I have tried this and got identical ("bad") results to
Test2::API::run_subtest:
~$
Actually at first glance a possible problem is this: You are using 2
functions that are not intended to be interchangeable.
Test::More::subtest() is a tool intended to run a subtest.
Test2::API::run_subtest() is a helper intended to write tools like
'subtest()'.
I would like to see the results wh
I will have to look into this when I have more time.
On Tue, Dec 13, 2016 at 8:06 AM, Ricardo Signes
wrote:
> I've hit a nasty (to me) difference between Test2::API::run_subtest and
> Test::Builder::subtest. Shout out to Matthew Horsfall for helping
> localize the
> problem. Here's my trivial
I've hit a nasty (to me) difference between Test2::API::run_subtest and
Test::Builder::subtest. Shout out to Matthew Horsfall for helping localize the
problem. Here's my trivial reproducer:
#!perl
use strict;
use warnings;
use Test::More;
use Test2::API;
my $code = sub {
if (for
