本文介绍了无法使用 java 类实例化名为异常的 @InjectMocks 字段的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我有一个带有用户定义构造函数的类.
I have a class with user defined constructor.
public class Employee
{
@Inject
private MyBean myBean;
private String abcd;
protected Employee(Parameter1 param1, Parameter2 param2)
{ //some operations on method params
//some operation on mybean
this.abcd = "some value";
}
protected String getAbcd()
{
return nrOfAccesses;
}
protected void setAbcd(String abcd)
{
this.abcd = abcd;
}
}
测试类
@RunWith(MockitoJUnitRunner.class)
public class TestEmployee
{
@Mock
private MyBean myBean;
private Parameter1 param1;
private Parameter2 param2;
@InjectMocks
private Employee employee;
@Before
public void prepare()
throws Exception
{
//some intialization
param1 = some value;
param2 = some value;
when(myBean.get(eq("ID"))).thenReturn("1075");
}
@Test
public void testEmployeeID()
{
employee = new Employee(param1, param2);
assertThat(employee.getAbcd(), is("XYZC"));
}
我遇到了异常
org.mockito.exceptions.base.MockitoException:
Cannot instantiate @InjectMocks field named 'employee' of type 'class com.xyz.Employee'.
You haven't provided the instance at field declaration so I tried to construct the instance.
However the constructor or the initialization block threw an exception : null
at org.mockito.internal.runners.JUnit45AndHigherRunnerImpl$1.withBefores(JUnit45AndHigherRunnerImpl.java:27)
at org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:254)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
at org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.lang.NullPointerException
推荐答案
如果你做了一个 employee = new Employee(param1, param2);
你不妨跳过 @InjectMocks代码>.
if you do a employee = new Employee(param1, param2);
you may as well skip @InjectMocks
.
它应该执行以下操作:
@InjectMocks
ClassUnderTest cut;
@Mock
Dependency1 dep1;
@Mock
Dependency2 dep2;
@Before
public void setup() {
initMocks(this);
}
省略 @InjectMocks
可以使用以下代码实现相同的行为:
omitting @InjectMocks
the same behaviour can be achieved with the following code:
ClassUnderTest cut;
@Mock
Dependency1 dep1;
@Mock
Dependency2 dep2;
@Before
public void setup() {
initMocks(this);
cut = new ClassUnderTest(dep1, dep2);
}
在您的具体情况下,您应该模拟 param1
和 param2
.使用 @InjectMocks
时切勿手动调用构造函数.
In your specific case, you should mock param1
and param2
. Never call the constructor manually when using @InjectMocks
.
这篇关于无法使用 java 类实例化名为异常的 @InjectMocks 字段的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!