Comments on: Testing without mocking framework

By: Building Blocks » Testing on Google AppEngine (Python SDK)

Building Blocks » Testing on Google AppEngine (Python SDK) — Mon, 28 Jun 2010 20:18:31 +0000

[...] Here is an example by AppEngine Fan where he uses Mocker to mock out the external API calls. An approach that shows the power of the mocking library, but to my taste it results in too much code, and too much details about the mocking framework in the test making it harder to read. This ties back to a previous post I wrote about testing without Mocks. [...]

By: Patrik Akselsson

Patrik Akselsson — Tue, 12 Jan 2010 21:51:54 +0000

I think the pattern you are looking for is “Test specific subclass”, http://xunitpatterns.com/Test-Specific%20Subclass.html

By: Johan A/ndersson

Johan A/ndersson — Tue, 12 Jan 2010 19:45:08 +0000

My discovery when we removed Rhino mocks was that we could swap services (such as an IDbConnection) the SUT used. The result is test cases separated from the arrangement of the SUT dependencies (again, such as the behavior/expectations of a database interface).
When arranged like this you could easily write ONE set of test cases for both unit and integration tests.
You can still use Rhino Mocks (or something else), but you will need to place your setup/expectations separate from your test fixture.
Then you need a mechanism to switch from mocked or non-mocked dependencies, perhaps different concrete test fixtures injecting the SUT dependencies using overridden abstract methods or something.

By: Morten

Morten — Tue, 12 Jan 2010 09:12:17 +0000

Hi Håkan!

The point is to consider if mocking really is the “fastest” tool for the job when writing the test. I’m not saying “don’t use mocking libraries”, I’m saying “consider not using mocking libraries, instead of just opting for using them”.

Depending on how you design you classes Mocking tools might just increase the burden, making it less clear what is under test, or just adding unnecessary coupling to mocking frameworks.

But yes, there are instances where you can get good results from a mocking framework. Just don’t mock blindly.

By: Håkan Forss

Håkan Forss — Tue, 12 Jan 2010 09:08:06 +0000

I think you just use the mock frameworks wrong. You are mocking things that should be part of the system under test just as you state.

Your sugested solution is just a way to mock without using a mock framework. Why would you not use a tool that help you do the same job but faster.