On 4/4/07, Philippe Bruhat (BooK) <[EMAIL PROTECTED]> wrote:
I've found myself passing parameters to some of my tests scripts. Usually because I want to run a specific subset of tests only.
...
Thoughts, anyone?
Wonderful idea. I'll take it off of my list of things to bring up someday. I often use my tests for debugging, especially where other modules are involved and I'm not sure where the fault is. Using modules like POE and Net::XMPP seems to cause the Eclipse Debugger to choke. Both distributions support turning on debugging output, which I turn on via a parameter to the test script. Sometimes it is just easier to debug through print than run the debugger anyway, but maybe I'm just missing something. In this case, it wouldn't be required to send it to all tests, but I don't see that as getting in the way. This would make prove way more useful for me. Somewhat related. I've been meaning to go back and figure out where 'prove' came from. I don't recall seeing any reference to it when I first went through the Test::Tutorial and other Test:: docs. It is very useful, but I found it by accident. Thanks -- 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.
