Comments on: Can I test what I want, please?

By: Java: Open Source Mocking Framework | Programming Resources

Java: Open Source Mocking Framework | Programming Resources — Fri, 24 Oct 2008 16:19:55 +0000

[...] intuitive approach: you ask questions about interactions after execution. Using mockito, you can verify what you want. Using expect-run-verify libraries you are often forced to look after irrelevant [...]

By: szczepiq

szczepiq — Thu, 13 Mar 2008 16:00:30 +0000

>aren’t your mocks in fact stubs?

They are spies. You can ask them questions about interactions. Effectively you can verify them.

>the library name

Only geeks see any relation to mocking. It’s all about drinking! :)

By: Marcin

Marcin — Thu, 13 Mar 2008 12:11:55 +0000

I’m not quite getting it.
Based on the example above, aren’t your mocks in fact stubs? They’re not verifying anything. So probably the library name is a little bit deprecated?
I personally like stubbing instead of mocking but I would like to have a library that can do both (rSpec does that).

By: szczepiq

szczepiq — Thu, 06 Mar 2008 23:20:01 +0000

>It seems like you’d end up writing two lines of code, one stub and one verify

Not really: stubs are implicitly verified – by the fact that stubbed value is essential for processing. Returned value is just more interesting… Do you remember the old days when we craft our stubs by hand? Did you ever verify your hand-written stubs?

> What if returning true from those two methods is important?

Then I’d stub it ;) In most cases an interaction is either asking (which I want to stub) or telling (which I want to verify).

By: Aaron Jensen

Aaron Jensen — Wed, 05 Mar 2008 14:45:33 +0000

It seems like you'd end up writing two lines of code, one stub and one verify in cases where you want to verify that something was called that also returns something that is important to the execution flow. On your google code you provide this example: EasyMock Control control = createStrictControl(); List one = control.createMock(List.class); List two = control.createMock(List.class); expect(one.add("one")).andReturn(true); expect(two.add("two")).andReturn(true); control.replay(); someCodeThatInteractsWithMocks(); control.verify(); Mockito List one = mock(List.class); List two = mock(List.class); someCodeThatInteractsWithMocks(); InOrder inOrder = inOrder(one, two); inOrder.verify(one).add("one"); inOrder.verify(two).add("two"); What if returning true from those two methods is important?