Re: Possible patch to Test::Pod

On Jun 7, 2012, at 10:20 AM, Russ Allbery wrote:

>> They do not.
> 
> That seems like something that maybe we could all agree could be done, no?
> This seems broader than just POD tests; the test failures may be due to
> some minor bit of functionality, or a change in the API of some other
> module for a part of the distribution that the person isn't planning on
> using.

How is the user to judge whether a test failure is serious or not?

Currently, when a user reports a failure to me, I can then tell them if it's safe to `force install`. But they generally have no idea how to tell the difference between an unimportant failure (e.g., bad expected path output in the test on Windows) and an important failure (the module will not work on this system).

David