Given all of this chat, what would folks think about an optional switch to 'runtests' (the TAPx::Parser equivalent to 'prove'), which would warn users about which test programs are being run without a plan?
Brilliant idea. In functional testing, there are situations where one doesn't know how many tests will be run. Say I am testing a web site to make sure that the copyright is included on every page. I don't want a plan, I just want to know if any pages fail (and which ones). How is this handled with pod checking? I think making it possible for the lack of a plan to be flagged when it is important retains Perl's inherent flexibility while supporting correctness when necessary. -- Eric Hacker, CISSP aptronym (AP-troh-NIM) noun A name that is especially suited to the profession of its owner I _can_ leave well enough alone, but my criteria for well enough is pretty darn high.
