CODEWITHSUNDEEP
javaunit-testingeasymock
Sara
Sara

Reputation: 2505

Persisting a mocked object with junit and easymock

So I have used easymock for mocking my data layer objects while unit testing. I am using JPA for persistency. E.g. Project project = EasyMock.cre..(Project.class); etc.

Now the method which I want to test gets this project does some stuff and then persists it calling persist(project). project is a mocked object so it throws me error here. My manager is telling me since you just want to test the functionality of the method. The return value from db is not imp that is why you should use mocking instead of real db. So in case of this method which has persist method call, what should I do?

Thanks.

Upvotes: 0

Views: 2904

Answers (1)

plasma147
plasma147

Reputation: 2211

You should be mocking the entity manager rather than the entity.

The entity is just a pojo that you can easily create, you need to see if the persist is called on the entity manager.

Edit

That looks like you are creating an instance of the entity manager in the test under class through a static method. There is no easy way to mock it out.

You should pass the Entity manager to the object that uses it using dependency injection. Then instead of passing the real implementation, you can just pass the mock instance.

So your code would look something like: 

Project project = ...    

EntityManager manager = EasyMock.createStrictMock(EntityManager.class); 
ClassUnderTest test = new ClassUnderTest(manager)

//You expect this to be called    
manager.persist(project);

EasyMock.replay(manager);

//The method you are testing
test.save(project);

EasyMock.verify(manager);

(I haven't used easymock for a while so the methods might not be quite right.)

Upvotes: 4

Related Questions