OP didn't post a question related to a Test::More script.

Unit testing questions are different, and the way I approach them is determined by whether the poster is the author of the test and the software behind it, or is simply having an issue during an install of software they want to use, but likely doesn't have any idea how the internals or its tests work.

I have gone on to supply patches to a good number of Open Source projects over the years because someone was having problems with unit tests of software they were simply trying to install and use, and I found bugs which I corrected.

Probably my question was too vague.

I believe that one of the most precise ways to describe a specific problem is by a Test::More script or something alike. The expected outcome will be at the bottom of the script in that case. The OP's example was not far away from such. Complaining about it appears to be more expensive than looking at this SSCCE.

And this thread definitely is :-)

Greetings,
-jo

$gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$

Throwing some code up and saying "help me fix it" without any indication what the code is supposed to do or isn't doing isn't efficient, even if it is a test file.

I see my time as valuable. I'm not about to go digging through code no matter what if there is no proper description of the actual problem. Informing those one is asking help of of what the actual situation is allows people to delve deeper, or decide whether the problem would be better solved by someone else.