Re: On Not Merging new and old behavior ( was Re: Test-Stream + MongoDB scalar refcount issue )

On Sat, May 2, 2015 at 3:03 PM, Stefan Seifert <[email protected]> wrote:

> What would that mean from a user perspective? Would one be able to mix
> Test::More and Test::More2 (and higher level modules based on them) in the
> same test file?
>

No, I meant that a .t file would have to choose one or the other.  So, for
example, if I had a Test::More2 .t file, I'd have to use Test::Fatal2,
Test::Deep2, etc. that are all built on Test::Builder2.

Meanwhile, anyone would still be free to have a .t file with Test::More,
Test::Fatal, etc.

There are only a handful of really commonly used Test::* libraries and I
suspect that they could be forked to use Test::Builder2 trivially, as few
of them wind up needing the interesting new bits.  Only the Test::* modules
that were monkey patching or can take advantage of hooks would need any
real revision.

David

-- 
David Golden <[email protected]> Twitter/IRC: @xdg