On 22 July 2017 at 17:18, Zefram <zefram@fysh.org> wrote: > > But you still get the broken behaviour. > But in most of those cases, the data you have makes the broken behaviour inconsequential. I've seen *reams* of test suites that have this problem simply because of the fun with needing to deal with marshalling your strings through Test::More. But the good thing is, the warnings are ignorable, they don't indicate any broken behaviour in place. The code they're warning about is external to the problem. It may produce some confusion for the person who reads the test output, but it does not demonstrate a real bug in the program under test. Making a test fail when there is no problem will simply encourage people to not run tests. -- Kent KENTNL - https://metacpan.org/author/KENTNLThread Previous | Thread Next