There is another problem with tests. Quite often to make a meaningfull test you have to ask the user some questions or ask him to do something. Eg. since most of the functions in Win32::FileOp are supposed to create some kind of dialogs I have to ask the user to click the dialogs off (OK, I would not have to. I could require that they have Win32::Setupsup installed and hope they will not interfere with the dialogs appearing and disappearing on their screen.
But what if the test is run by some automated tool. Eg. by the one ActiveStates use for their PPM repository. How do I as a module author?
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature