This is where prove comes in.

No. No. Absolutely no.

What you are saying is that if you use Test::* which produces all this extraneous garbage; then you can use this other tool -- with some set of magical incantations -- to throw that all(*) that garbage away. That is pure make-work.

I'll say it one last time. These modules: a) do nothing I can't more easily do myself; b) give me nothing extra I want; c) steal from me things I need; d) thus preventing me from obtaining things I value.

(*)Almost. You still get this fatuous bunch of crude:

Files=3, Tests=31,  1 wallclock secs ( 0.13 usr  0.03 sys +  0.33 cusr
+  0.03 csys =  0.52 CPU)
Result: PASS
[download]

Why would I care how many files there are or tests they contain? Am I going to decide to not install because there are too many files? Will I not reject it if they are all put into a single file? Or maybe I'll reject it if there are too few tests?

Why do I care how long the tests took to run? Either I was sat here waiting for it to complete, in which case I have a very good idea of how long it took -- measured on the scale of: it didn't take too long cos I didn't interrupt it. Or I was doing something else and don't care at all. Now, if they could tell me how long it is going to take; that would be of value. But telling me after the fact how long it took, is utterly pointless.

Finally, I've just seen "All tests successful"; what value does "Result: PASS" have?