t+1 - Latest Comments in I just wrote another mock object framework.

Re: I just wrote another mock object framework.

Matt Wilson — Mon, 29 Sep 2008 11:05:18 -0000

Consider that name stolen :)

Re: I just wrote another mock object framework.

Christian Wyglendowski — Mon, 29 Sep 2008 10:34:44 -0000

This is about the only mock object framework that I would use. The only thing it needs is a better name. OckMock - "The simplest answer is usually the correct answer."

Re: I just wrote another mock object framework.

Matt Wilson — Sat, 27 Sep 2008 08:53:34 -0000

Hi Ben,

I probably should have included a few example uses. Pretend I want to mock an object that has an attribute named ivr_sends which is a list of strings. I'd do this:

mm = BazMock(ivr_sends=['abc', 'def'])

Now my test code can access mm.ivr_sends just fine.

And now pretend you need to mock attributes on attributes:

mm = BazMock(x=BazMock(y=[BazMock(a=1, b=2), BazMock(a=3, b=4)]))

And now I can access mm.x.y[0].a.

For methods, you'd need to graft on definitions like this:

def fake_foo(x):
return "99"

mm.foo = fake_foo

I've been told that there are better mock objects out there, that do stuff like inspect a module or a class and create mocks automatically.

I'm dragging my feet about learning them. Let me know if you find one you like.

Re: I just wrote another mock object framework.

Ben Finney — Sat, 27 Sep 2008 01:51:40 -0000

Doesn't seem too useful; when the code under test attempts to call expected methods on an instance it'll fail with 'AttributeError'. A mock object should pretend it's the object being mocked, surely?

Re: I just wrote another mock object framework.

Michael Barton — Fri, 26 Sep 2008 17:36:41 -0000

Hey, you stole that code from my ORM.