网络上大部分是powermock 的用法,
PowerMock有两个重要的注解:
–@RunWith(PowerMockRunner.class)
–@PrepareForTest( { YourClassWithEgStaticMethod.class })
但是powermockito @PrepareForTest( { YourClassWithEgStaticMethod.class }) 是在使用时 每个test case 方法中按需添加的。 @RunWith(PowerMockRunner.class) 必须添加到类名头。
摘自:
http://blog.csdn.net/knighttools/article/details/44630975
一、为什么要使用Mock工具
在做单元测试的时候,我们会发现我们要测试的方法会引用很多外部依赖的对象,比如:(发送邮件,网络通讯,远程服务, 文件系统等等)。 而我们没法控制这些外部依赖的对象,为了解决这个问题,我们就需要用到Mock工具来模拟这些外部依赖的对象,来完成单元测试。
二、为什么要使用PowerMock
现如今比较流行的Mock工具如jMock、EasyMock 、Mockito等都有一个共同的缺点:不能mock静态、final、私有方法等。而PowerMock能够完美的弥补以上三个Mock工具的不足。
三、PowerMock简介
PowerMock是一个扩展了其它如EasyMock等mock框架的、功能更加强大的框架。PowerMock使用一个自定义类加载器和字节码操作来模拟静态方法,构造函数,final类和方法,私有方法,去除静态初始化器等等。通过使用自定义的类加载器,简化采用的IDE或持续集成服务器不需要做任何改变。熟悉PowerMock支持的mock框架的开发人员会发现PowerMock很容易使用,因为对于静态方法和构造器来说,整个的期望API是一样的。PowerMock旨在用少量的方法和注解扩展现有的API来实现额外的功能。目前PowerMock支持EasyMock和Mockito。
四、PowerMock入门
PowerMock有两个重要的注解:
–@RunWith(PowerMockRunner.class)
–@PrepareForTest( { YourClassWithEgStaticMethod.class })
如果你的测试用例里没有使用注解@PrepareForTest,那么可以不用加注解@RunWith(PowerMockRunner.class),反之亦然。当你需要使用PowerMock强大功能(Mock静态、final、私有方法等)的时候,就需要加注解@PrepareForTest。
五、PowerMock基本用法
(1) 普通Mock: Mock参数传递的对象
测试目标代码:
1 |
public boolean callArgumentInstance(File file) { |
测试用例代码:
02 |
public void testCallArgumentInstance() { |
04 |
File file = PowerMockito.mock(File. class ); |
06 |
ClassUnderTest underTest = new ClassUnderTest(); |
08 |
PowerMockito.when(file.exists()).thenReturn( true ); |
10 |
Assert.assertTrue(underTest.callArgumentInstance(file)); |
说明:普通Mock不需要加@RunWith和@PrepareForTest注解。
(2) Mock方法内部new出来的对象
测试目标代码:
01 |
public class ClassUnderTest { |
03 |
public boolean callInternalInstance(String path) { |
05 |
File file = new File(path); |
测试用例代码:
01 |
@RunWith (PowerMockRunner. class ) |
02 |
public class TestClassUnderTest { |
05 |
@PrepareForTest (ClassUnderTest. class ) |
06 |
public void testCallInternalInstance() throws Exception { |
08 |
File file = PowerMockito.mock(File. class ); |
10 |
ClassUnderTest underTest = new ClassUnderTest(); |
12 |
PowerMockito.whenNew(File. class ).withArguments( "bbb" ).thenReturn(file); |
14 |
PowerMockito.when(file.exists()).thenReturn( true ); |
16 |
Assert.assertTrue(underTest.callInternalInstance( "bbb" )); |
说明:当使用PowerMockito.whenNew方法时,必须加注解@PrepareForTest和@RunWith。注解@PrepareForTest里写的类是需要mock的new对象代码所在的类。
(3) Mock普通对象的final方法
测试目标代码:
1 |
public class ClassUnderTest { |
3 |
public boolean callFinalMethod(ClassDependency refer) { |
5 |
return refer.isAlive(); |
01 |
public class ClassDependency { |
03 |
public final boolean isAlive() { |
测试用例代码:
01 |
@RunWith (PowerMockRunner. class ) |
02 |
public class TestClassUnderTest { |
05 |
@PrepareForTest (ClassDependency. class ) |
06 |
public void testCallFinalMethod() { |
08 |
ClassDependency depencency = PowerMockito.mock(ClassDependency. class ); |
10 |
ClassUnderTest underTest = new ClassUnderTest(); |
12 |
PowerMockito.when(depencency.isAlive()).thenReturn( true ); |
14 |
Assert.assertTrue(underTest.callFinalMethod(depencency)); |
说明: 当需要mock final方法的时候,必须加注解@PrepareForTest和@RunWith。注解@PrepareForTest里写的类是final方法所在的类。
(4) Mock普通类的静态方法
测试目标代码:
1 |
public class ClassUnderTest { |
3 |
public boolean callStaticMethod() { |
5 |
return ClassDependency.isExist(); |
01 |
public class ClassDependency { |
03 |
public static boolean isExist() { |
测试用例代码:
01 |
@RunWith (PowerMockRunner. class ) |
02 |
public class TestClassUnderTest { |
05 |
@PrepareForTest (ClassDependency. class ) |
06 |
public void testCallStaticMethod() { |
08 |
ClassUnderTest underTest = new ClassUnderTest(); |
10 |
PowerMockito.mockStatic(ClassDependency. class ); |
12 |
PowerMockito.when(ClassDependency.isExist()).thenReturn( true ); |
14 |
Assert.assertTrue(underTest.callStaticMethod()); |
说明:当需要mock静态方法的时候,必须加注解@PrepareForTest和@RunWith。注解@PrepareForTest里写的类是静态方法所在的类。
(5) Mock 私有方法
测试目标代码:
01 |
public class ClassUnderTest { |
03 |
public boolean callPrivateMethod() { |
09 |
private boolean isExist() { |
测试用例代码:
01 |
@RunWith (PowerMockRunner. class ) |
02 |
public class TestClassUnderTest { |
05 |
@PrepareForTest (ClassUnderTest. class ) |
06 |
public void testCallPrivateMethod() throws Exception { |
08 |
ClassUnderTest underTest = PowerMockito.mock(ClassUnderTest. class ); |
10 |
PowerMockito.when(underTest.callPrivateMethod()).thenCallRealMethod(); |
12 |
PowerMockito.when(underTest, "isExist" ).thenReturn( true ); |
14 |
Assert.assertTrue(underTest.callPrivateMethod()); |
说明:和Mock普通方法一样,只是需要加注解@PrepareForTest(ClassUnderTest.class),注解里写的类是私有方法所在的类。
(6) Mock系统类的静态和final方法
测试目标代码:
01 |
public class ClassUnderTest { |
03 |
public boolean callSystemFinalMethod(String str) { |
09 |
public String callSystemStaticMethod(String str) { |
11 |
return System.getProperty(str); |
测试用例代码:
01 |
@RunWith (PowerMockRunner. class ) |
02 |
public class TestClassUnderTest { |
05 |
@PrepareForTest (ClassUnderTest. class ) |
06 |
public void testCallSystemStaticMethod() { |
08 |
ClassUnderTest underTest = new ClassUnderTest(); |
10 |
PowerMockito.mockStatic(System. class ); |
12 |
PowerMockito.when(System.getProperty( "aaa" )).thenReturn( "bbb" ); |
14 |
Assert.assertEquals( "bbb" , underTest.callJDKStaticMethod( "aaa" )); |
说明:和Mock普通对象的静态方法、final方法一样,只不过注解@PrepareForTest里写的类不一样 ,注解里写的类是需要调用系统方法所在的类。
六 、无所不能的PowerMock
(1) 验证静态方法:
PowerMockito.verifyStatic();
Static.firstStaticMethod(param);
(2) 扩展验证:
PowerMockito.verifyStatic(Mockito.times(2)); // 被调用2次 Static.thirdStaticMethod(Mockito.anyInt()); // 以任何整数值被调用
(3) 更多的Mock方法
http://code.google.com/p/powermock/wiki/MockitoUsage13
七、PowerMock简单实现原理
• 当某个测试方法被注解@PrepareForTest标注以后,在运行测试用例时,会创建一个新的org.powermock.core.classloader.MockClassLoader实例,然后加载该测试用例使用到的类(系统类除外)。
• PowerMock会根据你的mock要求,去修改写在注解@PrepareForTest里的class文件(当前测试类会自动加入注解中),以满足特殊的mock需求。例如:去除final方法的final标识,在静态方法的最前面加入自己的虚拟实现等。
• 如果需要mock的是系统类的final方法和静态方法,PowerMock不会直接修改系统类的class文件,而是修改调用系统类的class文件,以满足mock需求。
楼主代码:
- package com.ericsson.csp.cst.admin.util;
-
- import static org.junit.Assert.assertEquals;
-
- import java.io.IOException;
- import java.util.ArrayList;
- import java.util.Date;
- import java.util.List;
-
- import javax.ws.rs.core.Response;
-
- import org.codehaus.jackson.JsonGenerationException;
- import org.codehaus.jackson.map.JsonMappingException;
- import org.junit.Before;
- import org.junit.Test;
- import org.junit.runner.RunWith;
- import org.mockito.Mockito;
- import org.powermock.api.mockito.PowerMockito;
- import org.powermock.core.classloader.annotations.PrepareForTest;
- import org.powermock.modules.junit4.PowerMockRunner;
-
- import com.ericsson.csp.cst.admin.dao.entity.ResponseResult;
- import com.ericsson.csp.cst.admin.dao.entity.Syssubp;
- import com.ericsson.csp.cst.admin.service.SubscribeService;
- import com.ericsson.csp.cst.admin.service.SyssubpService;
-
- @RunWith(PowerMockRunner.class)
- public class SubscribeUtilTest{
-
- private Syssubp disp;
- private Syssubp fromdisp;
- private Syssubp nonSubscribedsubp;
- private Syssubp subscribedsubp;
-
- private SubscribeService subscribeService;
-
- private SyssubpService syssubpService;
-
- private SubscribeUtil subscribeUtil;
-
- @Before
- public void init() throws Exception{
- disp=fillInsubp();
- fromdisp=dispsubp();
- nonSubscribedsubp=getNonSubscribedLocalsubp();
- subscribedsubp=getSubscribedLocalsubp();
-
- syssubpService=PowerMockito.mock(SyssubpService.class);
- List<Syssubp> emptyLocalList=new ArrayList<Syssubp>();
- List<Syssubp> nonEmptyLocalList=new ArrayList<Syssubp>();
- nonEmptyLocalList.add(nonSubscribedsubp);
- PowerMockito.doReturn(nonEmptyLocalList).when(syssubpService,"query");
- PowerMockito.doNothing().when(syssubpService,"update",Mockito.any(Syssubp.class));
- PowerMockito.doNothing().when(syssubpService,"save",Mockito.any(Syssubp.class));
- PowerMockito.doNothing().when(syssubpService,"deleteById",Mockito.anyInt());
-
- subscribeService=PowerMockito.mock(SubscribeService.class);
- PowerMockito.doReturn(Response.status(200).type(new String()).entity("a string").build()).when(subscribeService,"subscribe",Mockito.any(Syssubp.class));
- PowerMockito.doReturn(Response.status(200).type(new String()).entity("a string").build()).when(subscribeService,"deletesubp",Mockito.anyInt());
- PowerMockito.when(subscribeService,"getAllsubps").thenReturn(Response.status(200).type(new String()).entity("a string").build());
-
- subscribeUtil=PowerMockito.spy(new SubscribeUtil());
- subscribeUtil.setSubscribeService(subscribeService);
- subscribeUtil.setsubpService(syssubpService);
- }
-
- @Test
- @PrepareForTest(SubscribeUtil.class)
- public void testSubscribe() throws Exception {
-
- String skip_createResponseResultByResponse="createResponseResultByResponse";
- String skip_createsubpBydispResponse="createsubpBydispResponse";
-
- ResponseResult result=new ResponseResult();
- result.setStatus(200);
-
- PowerMockito.doReturn(result).when(subscribeUtil, skip_createResponseResultByResponse, Mockito.any(Response.class),Mockito.any(ResponseResult.class));
- PowerMockito.doReturn(fromdisp).when(subscribeUtil, skip_createsubpBydispResponse, Mockito.any(ResponseResult.class));
-
- ResponseResult resp=subscribeUtil.subscribe(nonSubscribedsubp);
-
- assertEquals(200, resp.getStatus());
-
- }
-
- @Test
- public void testUpdatesubpLocally() throws JsonGenerationException, JsonMappingException, IOException{
-
- subscribeUtil.updatesubp(nonSubscribedsubp);
- }
-
- @Test
- @PrepareForTest(SubscribeUtil.class)
- public void testUpdatesubpdisply() throws Exception{
-
- ResponseResult result=new ResponseResult();
- result.setStatus(200);
-
- String skip_createResponseResultByResponse="createResponseResultByResponse";
- PowerMockito.doReturn(result).when(subscribeUtil, skip_createResponseResultByResponse, Mockito.any(Response.class),Mockito.any(ResponseResult.class));
- String skip_createsubpBydispResponse="createsubpBydispResponse";
- PowerMockito.doReturn(fromdisp).when(subscribeUtil, skip_createsubpBydispResponse, Mockito.any(ResponseResult.class));
-
- subscribeUtil.updatesubp(subscribedsubp);
- }
-
- @Test
- public void testDeletesubpLocally() throws Exception{
- PowerMockito.doReturn(nonSubscribedsubp).when(syssubpService,"queryById",Mockito.anyInt());
- subscribeUtil.deletesubp(100);
- }
- @Test
- @PrepareForTest(SubscribeUtil.class)
- public void testDeletesubpdisply() throws Exception{
- ResponseResult result=new ResponseResult();
- result.setStatus(200);
-
- PowerMockito.doReturn(subscribedsubp).when(syssubpService,"queryById",Mockito.anyInt());
- String skip_createResponseResultByResponse="createResponseResultByResponse";
- PowerMockito.doReturn(result).when(subscribeUtil, skip_createResponseResultByResponse, Mockito.any(Response.class),Mockito.any(ResponseResult.class));
-
- subscribeUtil.deletesubp(100);
- }
-
- @Test
- @PrepareForTest({JacksonUtil.class,SubscribeUtil.class})
- public void testSyncdispWhenLocalNonEmpty() throws Exception{
- ResponseResult result=new ResponseResult();
- result.setStatus(200);
- String skip_createResponseResultByResponse="createResponseResultByResponse";
- PowerMockito.doReturn(result).when(subscribeUtil, skip_createResponseResultByResponse, Mockito.any(Response.class),Mockito.any(ResponseResult.class));
-
- List<Syssubp> dispList=new ArrayList<Syssubp>();
- dispList.add(fromdisp);
- dispList.add(fromdisp);
- dispList.add(fromdisp);
-
- PowerMockito.mockStatic(JacksonUtil.class);
- PowerMockito.when(JacksonUtil.getListByTargetClass(Mockito.anyString(), Mockito.eq(Syssubp.class))).thenReturn(dispList);
-
- subscribeUtil.syncSubcriptionWithdisp();
- }
-
- @Test
- @PrepareForTest({JacksonUtil.class,SubscribeUtil.class})
- public void testSyncdispWhenLocalEmpty() throws Exception{
- ResponseResult result=new ResponseResult();
- result.setStatus(200);
- String skip_createResponseResultByResponse="createResponseResultByResponse";
- PowerMockito.doReturn(result).when(subscribeUtil, skip_createResponseResultByResponse, Mockito.any(Response.class),Mockito.any(ResponseResult.class));
-
- List<Syssubp> dispList=new ArrayList<Syssubp>();
- dispList.add(fromdisp);
- dispList.add(fromdisp);
- dispList.add(fromdisp);
-
- PowerMockito.mockStatic(JacksonUtil.class);
- PowerMockito.when(JacksonUtil.getListByTargetClass(Mockito.anyString(), Mockito.eq(Syssubp.class))).thenReturn(dispList);
-
- List<Syssubp> emptyLocalList=new ArrayList<Syssubp>();
- PowerMockito.doReturn(emptyLocalList).when(syssubpService,"query");
-
- subscribeUtil.syncSubcriptionWithdisp();
- }
-
- private Syssubp fillInsubp() {
- Syssubp syssubp=new Syssubp();
- syssubp.setCallbackUrl("http://192.168.3.237:8080/cst-ecall/services/uplink/uplinkService");
- syssubp.setTopicServiceId("adade");
- syssubp.setEnableTransformation(true);
- syssubp.setUsername("");
- syssubp.setPassword("");
- return syssubp;
- }
- private Syssubp getNonSubscribedLocalsubp() {
- Syssubp syssubp=new Syssubp();
- syssubp.setCallbackUrl("http://192.168.3.237:8080/cst-ecall/services/uplink/uplinkService");
- syssubp.setTopicServiceId("adade");
- syssubp.setEnableTransformation(true);
- syssubp.setUsername("");
- syssubp.setPassword("");
- syssubp.setApp_name("app");
- syssubp.setCreate_time(new Date());
- syssubp.setId(100);
- return syssubp;
- }
- private Syssubp getSubscribedLocalsubp() {
- Syssubp syssubp=new Syssubp();
- syssubp.setCallbackUrl("http://192.168.3.237:8080/cst-ecall/services/uplink/uplinkService");
- syssubp.setTopicServiceId("adade");
- syssubp.setEnableTransformation(true);
- syssubp.setUsername("");
- syssubp.setPassword("");
- syssubp.setApp_name("app");
- syssubp.setCreate_time(new Date());
- syssubp.setId(100);
- syssubp.setStatus(true);
- syssubp.setUpdate_time(new Date());
- syssubp.setsubpId(100);
- return syssubp;
- }
-
- private Syssubp dispsubp() {
- Syssubp syssubp=new Syssubp();
- syssubp.setCallbackUrl("http://192.168.3.237:8080/cst-ecall/services/uplink/uplinkService");
- syssubp.setTopicServiceId("adade");
- syssubp.setEnableTransformation(true);
- syssubp.setUsername("");
- syssubp.setPassword("");
- syssubp.setsubpId(100);
- return syssubp;
- }
- }
- PowerMock用法[转]
转:http://agiledon.github.io/blog/2013/11/21/play-trick-with-powermock/ 当我们面对一个遗留系统时,常见的问题是没有测试.正如Mic ...
- powerMock比easyMock和Mockito更强大(转)
powerMock是基于easyMock或Mockito扩展出来的增强版本,所以powerMock分两种类型,如果你习惯于使用easyMock的,那你就下载基于easyMock的powerMock,反 ...
- PowerMockito使用详解(转)
一.为什么要使用Mock工具 在做单元测试的时候,我们会发现我们要测试的方法会引用很多外部依赖的对象,比如:(发送邮件,网络通讯,远程服务, 文件系统等等). 而我们没法控制这些外部依赖的对象,为了解 ...
- PowerMockito使用详解
一.PowerMock概述 现如今比较流行的Mock工具如jMock,EasyMock,Mockito等都有一个共同的缺点:不能mock静态.final.私有方法等.而PowerMock能够完美的弥补 ...
- mock测试之powermock
由于公司框架依赖别的模块, 导致我们开发老是需要跟着他们的脚步, 所以我的上级领导提出这个方案说直接跳过他们,我们自己在本地测试,然后就找了它, 导入相关jar <dependency> ...
- 使用PowerMockito和Mockito进行模拟测试,包括静态方法测试,私有方法测试等,以及方法执行的坑或者模拟不成功解决
依赖:这个很重要,不同版本用法也有点区别: <dependency> <groupId>org.mockito</groupId> <artifactId&g ...
- PowerMock介绍
一.为什么要使用Mock工具 在做单元测试的时候,我们会发现我们要测试的方法会引用很多外部依赖的对象,比如:(发送邮件,网络通讯,远程服务, 文件系统等等). 而我们没法控制这些外部依赖的对象,为了解 ...
- PowerMock单元测试
在Java程序的单元测试中常用的mock工具有Mockito和EasyMock.但是这两种mock工具都无法实现对静态.final.私有方法或类的mock.因此有了功能强大的PowerMock工具.P ...
- PowerMock学习之PoweMock的入门(二)
前言 在上一篇<PowerMock学习之PoweMock的入门(一)>文章中,已经简单提及一些关于powermock的用法,但是入门还未完,我还要坚持把它学习并坚持更新到博客中. Mock ...
随机推荐
- require.js的用法
我采用的是一个非常流行的库require.js. 一.为什么要用require.js? 最早的时候,所有Javascript代码都写在一个文件里面,只要加载这一个文件就够了.后来,代码越来越多,一个文 ...
- 发现了一个制作iOS图标的利器
我制作的第一个Swift Demo已经将近完工,今天的任务便是给它添加图标.不过Xcode中对图标尺寸的要求还真是严苛,若是制作iPhone和iPad通用的应用,总共需要12种尺寸的图标,这对于美工功 ...
- 深入浅出TCP/IP簇
TCP/IP是“transmission Control Protocol/Internet Protocol”的简写,中文译名为传输控制协议/互联网络协议.TCP/IP不是一个协议,而是一个协议簇的 ...
- QT实现软件重启
//重启软件 void MainWindow::on_pushButton_UI_reboot_clicked() { //方式1 需要主函数中事件循环判断 //qApp->exit(773); ...
- Valid Palindrome
leetcode:https://oj.leetcode.com/problems/ 今天A了一个Easy类型的,主要是判断一个字符串是否是回文.东平西凑的还是给弄好了,具体可看下面的要求,或者直接去 ...
- Visual Studio 2013 各版本注册码
Visual Studio Ultimate 2013 KEY(密钥):BWG7X-J98B3-W34RT-33B3R-JVYW9 Visual Studio Premium 2013 KEY(密钥) ...
- Codeforces Round #354 (Div. 2) C. Vasya and String
题目链接: http://codeforces.com/contest/676/problem/C 题解: 把连续的一段压缩成一个数,对新的数组求前缀和,用两个指针从左到右线性扫一遍. 一段值改变一部 ...
- BZOJ3874 codevs3361 宅男计划
AC通道1:http://www.lydsy.com/JudgeOnline/problem.php?id=3874 AC通道2:http://codevs.cn/problem/3361/ [题目分 ...
- Nginx的accept_mutex配置分析
让我们看看accept_mutex的意义:当一个新连接到达时,如果激活了accept_mutex,那么多个Worker将以串行方式来处理,其中有一个Worker会被唤醒,其他的Worker继续保持休眠 ...
- C51关键字
C51 中的关键字 关键字 用途 说明 auto 存储种类说明 用以说明局部变量,缺省值为此 break 程序语句 退出最内层循环 case 程序语句 Switch语句中的选择项 char 数据类型说 ...