how about the old and simple: import ExpensiveModuleStub as ExpensiveModule
On a different league you could make use of decorator and creating caching objects but that depends entirely on the requirements (how strict your test must be, test data sizes involved and more, much more details). Regards, Antonio On Saturday 23 May 2009 14:00:15 pigmart...@gmail.com wrote: > Hi, > > I'm working on a unit test framework for a module. The module I'm > testing indirectly calls another module which is expensive to access > --- CDLLs whose functions access a database. > > test_MyModule --->MyModule--->IntermediateModule--- > > >ExpensiveModule > > I want to create a stub of ExpensiveModule and have that be accessed > by IntermediateModule instead of the real version > > test_MyModule --->MyModule--->IntermediateModule--- > > >ExpensiveModuleStub > > I tried the following in my unittest: > > import ExpensiveModuleStub > sys.modules['ExpensiveModule'] = ExpensiveModuleStub # Doesn't > work > > But, import statements in the IntermediateModule still access the real > ExpensiveModule, not the stub. > > The examples I can find of creating and using Mock or Stub objects > seem to all follow a pattern where the fake objects are passed in as > arguments to the code being tested. For example, see the "Example > Usage" section here: http://python-mock.sourceforge.net. But that > doesn't work in my case as the module I'm testing doesn't directly use > the module that I want to replace. > > Can anybody suggest something? > > Thanks, > > Scott -- http://mail.python.org/mailman/listinfo/python-list
