Comments on: expect-run-verify… Goodbye!

By: знакомства транс

знакомства транс — Thu, 17 Dec 2009 17:28:55 +0000

и всё эе: мне понравилось..

By: Padcom

Padcom — Fri, 10 Apr 2009 14:39:03 +0000

Going over some talks on TechNet and Google Video I’ve discovered points of view about using mock frameworks that I’d never ever expect. For example some people seem to bring up the point that while using mocking frameworks is not inherently bad they do tend to hide the additional complexity that your interfaces might introduce. The reason for that was that if your interface is to big and you’re using Moq instead of creating an instance of it by yourself you will run into unnecessary dependencies and not even see it coming.
Even though I understand those kind of arguments I still believe that both Moq and Mockito are great frameworks and you know what? I use both all the time

Keep up the good work!

By: wuetender-junger-mann.de » Blog Archive » More Thoughts about Mocking and State

Sun, 04 May 2008 18:58:34 +0000

[...] end of the request, state is all that’s left). Some people argued for some kind of general state machine implementation in the mocking framework. I think this is utterly wrong. If you are writing java [...]

By: szczepiq

szczepiq — Thu, 06 Mar 2008 23:09:36 +0000

Mockito can’t do that. For example, how can you say that in one state...

Are you complaining about the fact that Mockito mocks are stateless? Well, that's the point! Mocks are lightweight, test-drive is a pleasure, test code is clean & simple which hopefully pushes the app code to be simple. We're always open to suggestions, though. Show us an example from your code where you use mocking and mockito wouldn't help you. So far, I have no problems in verifying behaviour using mockito.

Abstract state machines one of the fundamental design techniques of OO programming, the stuff they teach in the first year programming courses at university. But Mockito can’t work with it...

Simple and clean code is one of the fundamental techniques of building successful software, the stuff one learns in the first year of working as a software developer. Mockito shines in that respect.

By: James

James — Wed, 05 Mar 2008 21:11:22 +0000

It sounds like you are thinking about objects in the wrong way and that’s why you are getting tied up in knots by expectations.

You should not be thinking about “expect/run/verify” or the internal data stored in your objects.

You should be thinking about the communication between your objects and describing those messaging patterns.

Mockito can’t do that. For example, how can you say that in one state a query method is stubbed to return value A, then a single call to a command method puts the object into a state in which the query method will return value B.

Abstract state machines one of the fundamental design techniques of OO programming, the stuff they teach in the first year programming courses at university. But Mockito can’t work with it. It’s only barely useful for OO programming.

By: Revue de Presse Xebia par J2EE, Agilité et SOA : Le blog de Xebia France

Mon, 03 Mar 2008 18:32:55 +0000

[...] Faber nous présente dans expect-run-verify… Goodbye! les raisons qui l’ont poussé à créer un nouveau framework de mocks – Mockito – en partant [...]