【问题标题】:Mock and verify 2 methods public static void and public static boolean from same class using PowerMockito使用 PowerMockito 模拟和验证来自同一类的 2 个方法 public static void 和 public static boolean
【发布时间】:2016-04-04 09:23:33
【问题描述】:

我有一堂课说ClassA,它必须有3-4个public static方法,我的要求是模拟2个方法,一个是public static void,另一个是public static boolean

下面的代码sn-p

class ClassA{
   public static boolean isConnected(){
     //....
   }
   public static void doSomething(){
    //....
   }
  public static void doSomethingMore(){
    //....
   }
}

现在我有另一个班级说ClassBmethod1() 调用ClassA.isConnected()ClassA.doSomething() 如下

class ClassB{
   public void method1(){
      if(ClassA.isConnected()){
        //...
      }else{
        ClassA.doSomething()
      }
   }
}

现在我想对method1() 进行单元测试,所以我尝试使用PowerMockito 模拟isConnected()doSomething(),如下所示

@RunWith(PowerMockRunner.class)
@PrepareForTest({ClassA.class})
public class ClassBTest{ 

@Test
public void testMethod1{
     //variables
     ClassB classB = new ClassB();
    //mock static non-void method
    PowerMockito.mockStatic(ClassA.class);
    PowerMockito.when(ClassA.isConnected()).thenReturn(false);
    //mock static void method
    PowerMockito.doNothing().when(ClassA.class);
    ClassA.doSomething();
    //execute
    classB.method1();

    //verify static non-void method called
    PowerMockito.verifyStatic(times(1)); 
    ClassA.isConnected();
    //Verify static void method called
    PowerMockito.verifyStatic(times(1)); 
    **ClassA.doSomething();**//getting error at this line
 }
}

错误:

Wanted but not invoked com.example.utils.common.ClassA.doSomething(
    );

However, there were other interactions with this mockcom.example.utils.common.ClassA.isConnected();

com.example.utils.common.ClassA.doSomethingMore(
    );

.
    at org.powermock.core.MockGateway.doMethodCall(MockGateway.java:124)
    at org.powermock.core.MockGateway.methodCall(MockGateway.java:63)
    at com.example.utils.common.ClassA.doSomething(ClassA.java)
    at com.example.utils.common.ClassBTest.testMethod1(ClassBTest.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:68)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:310)
    at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:89)
    at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:97)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.executeTest(PowerMockJUnit44RunnerDelegateImpl.java:294)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTestInSuper(PowerMockJUnit47RunnerDelegateImpl.java:127)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
    at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
    at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:207)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:146)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
    at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
    at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
    at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:122)
    at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:106)
    at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
    at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
    at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:78)
    at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212)
    at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)

【问题讨论】:

  • 也许你的方法不应该是静态的............为你节省了很多问题
  • 不确定,但为什么是PowerMockito.spy(ClassA.class); 行?首先你嘲笑它,然后你告诉它你只是想监视?我倾向于不使用 PowerMockito - 重构通常是更好的选择 - 但这听起来有点奇怪。
  • @Blundell : 这是现有项目...添加单元测试。
  • @FlorianSchaetz 该行是拼写错误。它不在测试用例中,我稍后将其从问题中删除。请尝试这种情况。如果你得到答案
  • 在我将times(2)times(1) 切换为isConnected() 验证后,代码对我来说很好(模拟准备不算在内)。然后它成功了,没有任何麻烦。

标签: java android unit-testing mockito powermockito


【解决方案1】:

作为正确模拟静态的替代方法。您可以修改遗留代码以提高可测试性。

下面的示例保留了静态方法,以防它们在代码库的其他地方使用。显然,一旦删除了所有静态方法调用,您就可以从这里删除它们(然后也删除 instance)。

class ClassA{
   private static ClassA instance = new ClassA();

   public static boolean isConnected(){
     return instance.isConnected();
   }

   public boolean isConnected(){
     //....
   }

   public static void doSomething(){
    instance.doSomething();
   }

   public void doSomething(){
    //....
   }       

   public static void doSomethingMore(){
    instance.doSomethingMore();
   }

   public void doSomethingMore(){
    //....
   }
}

ClassB 有一个 setter,您可以根据您的代码将其更改为构造函数依赖项或注入框架。 setter 是包保护的,因此它的可见性最小。 annotation VisibleForTesting 是可选的,只是突出显示设置器的原因。

class ClassB{

   private ClassA classA = new ClassA();

   @VisibleForTesting
   void setClassA(ClassA classA) {
        this.classA = classA;
   }

   public void method1(){
      if(classA.isConnected()){
        //...
      }else{
        classA.doSomething()
      }
   }
}

无需PowerMock即可简化测试:

public class ClassBTest{ 

@Test
public void testMethod1{
     //variables
     ClassB classB = new ClassB();
     ClassA mockClassA = Mockito.mock(ClassA.class);
     classB.setClassA(mockClassA);
     // mock expected behaviour
     Mockito.when(mockClassA.isConnected()).thenReturn(false);

    //execute
    classB.method1();

    Mockito.verify(mockClassA, times(2)).isConnected();
    Mockito.verify(mockClassA).doSomething();
 }
}

【讨论】:

  • 我个人更喜欢构造函数注入来进行这种测试,但效果是一样的。
  • @FlorianSchaetz 一样,我在 desc 中写过,但我不知道他的遗留代码的状态,所以试图最小化中断
  • 您好,有什么方法可以在不更改遗留源代码的情况下编写测试用例。 PowerMockito 支持 Mocking Static 方法code.google.com/p/powermock/wiki/MockitoUsage13
  • @PallaviG 你怎么不想/不能清理代码?
  • @PallaviG.,这就是 PowerMock 的用途——如果你真的无法重构有问题的代码(这也可能发生,例如,如果你绑定到一些代码质量有问题的框架) .正如我上面写的,代码对我有用,也许你在这里遇到了一些版本问题。
猜你喜欢
  • 1970-01-01
  • 2016-05-22
  • 2023-03-14
  • 1970-01-01
  • 1970-01-01
  • 2019-05-28
  • 1970-01-01
  • 1970-01-01
  • 2012-08-10
相关资源
最近更新 更多