Why should I use mock objects (Java)? Do all mocking frameworks serve the same purpose?

Question

Possible Duplicate:
What is the purpose of mock objects?

I'm preparing a presentation and I need to get a better understanding of what mocking is, what is the purpose of using it, what are the common situations that I should use mock objects? I found out that there are a bunch of mocking frameworks out there. Do they all do the same thing or do I use a specific framework for specific testing purpose? What are the differences between these frameworks? Which one would you recommend for testing Java?

here are some stuff that I found:

1.MockingToolkitComparisonMatrix which seems biased.

2.What are mock objects in Java? This is a year old. I thought there might be some better answer today.

Thank you.

score 6 · Accepted Answer · answered Jun 21 '11 at 13:40

The purpose of mocking is to allow you to test your application components in isolation. For example, if you have a service that uses a DAO, you want to be able to test your service without actually having to go to the database via the DAO. You would

1) Test the DAO in isolation, and
2) Mock the DAO in your service tests, so your service can be tested in isolation.

Since your DAO has a clearly defined API, your mock DAO simulates that API. So if you have a findAll type method that your service calls, you can easily mock the DAO to expect a call to findAll and return the appropriate results.

The purpose of all mocking frameworks is the same -- to allow you to set up expectations and assert that those expectations were met in your tests. The details, however, are different between frameworks. I have used EasyMock in actual work environments, and played around with Mockito for answering a few questions on SO. Both are pretty nice. The cost of entry is fairly low -- the idea is always to set up expectations, get the mock to return the results, and then to verify that the expectations were met. You might have to take a day or 2 to understand your mocking framework, but after that you should be able to be productive and figure out what you don't know as you go.

So in any case of dependancy, I should be using a mock object to isolate the class that I'm testing. — , Jun 21 '11 at 13:59
I recommend Mockito - concise syntax, supports non-strict verification, and has plenty of features. — Garrett Hall, Jun 21 '11 at 14:09
@gnon, yeah, mockito was pretty nice from what I saw. Does it support mocking concrete classes as opposed to just interfaces? — hvgotcodes, Jun 21 '11 at 14:31
Yes, but nothing final/static. For that there is a PowerMock version. — Garrett Hall, Jun 21 '11 at 22:23

score 5 · Answer 2 · answered Jun 21 '11 at 14:11

5

In a good encapsulated design, a class should behave the same regardless of the implementation classes of its dependencies. Mocking allows you to isolate your implementation code such that you can inspect how it will react independent of more volatile constructs such as databases and file systems in a way that ensures a deterministic outcome.

answered Jun 21 '11 at 14:11

nsfyn55

14,875
8
50
77

I think you just spoke like TDD Guru! What a wordings! – asyncwait Jul 06 '13 at 09:11

score -1 · Answer 3 · answered Jun 21 '11 at 13:56

A mock framework also should help to define that a certain method got called during a test.

So if your test does not call the specified method the mock framework will indicate that. Or you could specify that two methods are called in a specific order (open/close e.g.)

Why should I use mock objects (Java)? Do all mocking frameworks serve the same purpose?

3 Answers3