Re^2: change perl function in runtime

I have to disagree with you. This is a perfectly reasonable request. In fact, this is considered a good practice for testing complex software.

There are lots of reasons for doing things like this:

You may not have control over function y
It might do something that you don't want to do during testing (such as submit a credit card order...)
It might take a long time to run.
It might be hard to reproduce certain kinds of output.
It might not be written yet, or it might have bugs of its own (simulating part of the software allows you to develop/test multiple interdependent pieces of code simultaneously).

When's the last time you used duct tape on a duct? --Larry Wall

Comment on Re^2: change perl function in runtime

Replies are listed 'Best First'.
Re^3: change perl function in runtime by space_monk (Chaplain) on Dec 03, 2012 at 19:21 UTC
Thanks for the reasons. I normally suppress things I don't want to do during a test run, but I can see your points :-) A Monk aims to give answers to those who have none, and to learn from those who know more.	[reply]
Re^4: change perl function in runtime by ColonelPanic (Friar) on Dec 04, 2012 at 08:43 UTC
Obviously, changing function calls at run time is not the only way to overcome the above problems. The important thing is using good testing principles, rather than a particular implementation. I think it is a useful and powerful tool for certain kinds of testing. When's the last time you used duct tape on a duct? --Larry Wall	[reply]