Bram Smeets Blog

Comment by Herryanto Siatono

January 20, 2006 @ 1:16 pm

The new features look very much similar to JMock, anyway those new methods will come in handy.

Comment by Alexxzwc

February 11, 2007 @ 2:21 am

Hello, my name is Alex, i’m a newbie here. I really do like your resource and really interested in things you discuss here, also would like to enter your community, hope it is possible:-) Cya around, best regards, Alex!

Comment by JJ

February 15, 2007 @ 11:37 pm

Hi, I’m trying to use EasyMock as you suggested. Here is what my tests look like:

I’m getting null in my assertEquals(”person1″, person.getFirstname());

public class PersonManagerIntegrationTests extends AbstractJpaTests {

private PersonManager personManager = createMock(PersonManager.class);
private Person person;
private List personList;

protected String[] getConfigLocations() {
return new String[] {”classpath:/*/applicationContext.xml”};
}

protected void onSetUpInTransaction() throws Exception {
jdbcTemplate.execute(”insert into person (id, firstname, lastname, dob, job) values (2, ‘person1′, ‘name1′, ‘01/01/2001′, ‘IT’)”);
jdbcTemplate.execute(”insert into person (id, firstname, lastname, dob, job) values (3, ‘person2′, ‘name2′, ‘01/01/2001′, ‘IT’)”);
jdbcTemplate.execute(”insert into person (firstname, lastname, dob, job) values (’person3′, ‘name3′, ‘01/01/2001′, ‘IT’)”);
jdbcTemplate.execute(”insert into person (firstname, lastname, dob, job) values (’person4′, ‘name4′, ‘01/01/2001′, ‘IT’)”);
jdbcTemplate.execute(”insert into person (firstname, lastname, dob, job) values (’person5′, ‘name5′, ‘01/01/2001′, ‘IT’)”);
}

public void testFindById() {
expect(personManager.findById(”2″)).andReturn(new Person()).times(1);
replay(personManager);
person = personManager.findById(”2″);

assertNotNull(person);
assertEquals(”person1″, person.getFirstname());
verify(personManager);
}

Comment by Bram Smeets

February 18, 2007 @ 11:07 pm

Hi JJ,
It seems to me that you are testing the wrong thing. You typically want to test the real PersonManager class and use EasyMock to mimic the behavior of collaborator objects.

In this case, you are using an integration test (AbstractJpaTests) to test your manager. You insert data into the database in the onSetupInTransaction method. So it seems to me that you do NOT want to use EasyMock to create a mock object.

If you only want to test the implementation of the manager (so without the integration with the database) then you would want to use EasyMock.

In that case, you want to create a mock version of for instance the DAO that the manager uses to retrieve the data. So you do NOT create a mock for the object you want to test, but for the collaborator objects.

I hope this helps,
Bram

Comment by JJ

February 20, 2007 @ 1:00 am

Hi Bram,

Thanks for the response. I’m still not clear on just testing the PersonManager class. I’m getting Unexpected method call findById(”1″) error in my testSavePerson(). I can’t test removePerson, it’s saying The method expect(T) in the type EasyMock is not applicable for the arguments(void). Am I doing something wrong?

public class PersonManagerTest extends TestCase {
private PersonDao personDaoMock;
private PersonManager personManagerMock;
private Person person = null;

protected void setUp() throws Exception {
super.setUp();
personDaoMock = createMock(PersonDao.class);
personManagerMock = createMock(PersonManager.class);
}

public void testFindById() throws Exception {
expect(personManagerMock.findById(”1″)).andReturn(new Person());
replay(personManagerMock);
person = personManagerMock.findById(”1″);
verify(personManagerMock);
assertTrue(person != null);
}

public void testSavePerson() throws Exception {
person = new Person();
person.setFirstname(”John”);
person.setLastname(”Doe”);
person.setDob(new Date(”12/12/2000″));
person.setJob(”IT”);
expect(personManagerMock.savePerson(person)).andReturn(person);
replay(personManagerMock);
person = personManagerMock.savePerson(person);
verify(personManagerMock);

reset();
expect(personManagerMock.findById(”1″)).andReturn(new Person());
replay(personManagerMock);
person = personManagerMock.findById(”1″);
verify(personManagerMock);
assertTrue(person != null);
assertEquals(person.getFirstname(), “John”);

}

public void testRemovePerson() throws Exception {
expect(personManagerMock.removePerson(”1″));
}

Comment by Bram Smeets

February 20, 2007 @ 12:56 pm

You are still creating a mock object for the PersonManager. You should change your setUp() method to something like:

protected void setUp() throws Exception {
personDaoMock = createMock(PersonDao.class);
personManager = new PersonManagerImpl();
personManager.setPersonDao(personDaoMock);
}

And then record the behavior on the DAO and then in the test call the PersonManager methods (which will subsequently call the DAO.

Comment by Kiran

October 9, 2007 @ 8:08 am

What about number of times for a void method call?

Comment by Bram Smeets

October 9, 2007 @ 4:15 pm

I’m not 100% sure, but I think you can use expectLastCall().times(6); or something similar.

Comment by KV

January 9, 2008 @ 9:34 pm

Question. I posted a Q in the easymock forum. Got a response, but I am still stuck.

bottom line, I have a private method call from a public method. Easy mock is failing with an assertion error. How am I supposed to handle this

http://tech.groups.yahoo.com/group/easymock/message/1104