服務層測試使用了EasyMock

Question

服務接口：

public List<UserAccount> getUserAccounts(); 
public List<UserAccount> getUserAccounts(ResultsetOptions resultsetOptions, List<SortOption> sortOptions); 

服務實現：

public List<UserAccount> getUserAccounts() { 
    return getUserAccounts(null, null); 
} 
public List<UserAccount> getUserAccounts(ResultsetOptions resultsetOptions, List<SortOption> sortOptions) { 
    return getUserAccountDAO().getUserAccounts(resultsetOptions, sortOptions); 
} 

如何測試這個使用了EasyMock或任何其他可行的測試方法？示例代碼將不勝感激。對於容易的模擬傳遞對象作爲參數非常混亂。有人清楚地解釋什麼是測試服務層的最佳方法？測試服務接口將被視爲單元測試還是集成測試？

Answer 1

在這裏，你走了，假設你使用JUnit 4註釋：

import static org.easymock.EasyMock.createStrictMock; 
import static org.easymock.EasyMock.expect; 
import static org.easymock.EasyMock.replay; 
import static org.easymock.EasyMock.verify; 

public class UserAccountServiceTest 

    private UserAccountServiceImpl service; 
    private UserAccountDAO mockDao; 

    /** 
    * setUp overrides the default, We will use it to instantiate our required 
    * objects so that we get a clean copy for each test. 
    */ 
    @Before 
    public void setUp() { 
      service = new UserAccountServiceImpl(); 
      mockDao = createStrictMock(UserAccountDAO.class); 
      service.setUserAccountDAO(mockDao); 
    } 

    /** 
    * This method will test the "rosy" scenario of passing a valid 
    * arguments and retrieveing the useraccounts. 
    */ 
    @Test 
    public void testGetUserAccounts() { 

      // fill in the values that you may want to return as results 
      List<UserAccount> results = new User(); 

      /* You may decide to pass the real objects for ResultsetOptions & SortOptions */ 
      expect(mockDao.getUserAccounts(null, null) 
       .andReturn(results); 

      replay(mockDao); 
      assertNotNull(service.getUserAccounts(null, null)); 
      verify(mockDao); 
    } 

} 

您也可能會發現this article有用的，特別是如果你在JUnit 4中使用JUnit 3

Refer this一個快速的幫助

希望有幫助。