blocks|key|169271|text|使用@Spy注释|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|169272|@RunWith(MockitoJUnitRunner.class)
public+class+DemoTest+{
++++@Spy
++++private+SomeService+service+=+new+RealServiceImpl();

++++@InjectMocks
++++private+Demo+demo;

++++/*+...+*/
}|code-block|syntax|javascript|169273|Mockito将考虑所有具有@Mock或@Spy注释的字段作为潜在的候选字段，以将其注入到带有@InjectMocks注释的实例中。在上面的例子中，'RealServiceImpl'实例将被注入到“演示”中。|169274|有关详细信息，请参阅|169275|Mockito-home|169276|@Spy|169277|@Mock|169278|entityMap|0|LINK|mutability|MUTABLE|url|http://site.mockito.org/|1|https://static.javadoc.io/org.mockito/mockito-core/2.18.3/org/mockito/Spy.html|2|https://static.javadoc.io/org.mockito/mockito-core/2.18.3/org/mockito/Mock.html^0|2|4|0|0|E|5|K|4|1B|C|22|H|0|0|0|C|0|0|0|4|1|0|0|5|2|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1J|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1K|8|@]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|Q|3|R|5|6|7|1O|8|@]|D|@$9|1P|A|1Q|1|1R]]|E|$]]|$1|S|3|T|5|6|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|U|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]|14|$5|X|Y|Z|E|$10|15]]]]

Use <code>@Spy</code> annotation

<pre><code>@RunWith(MockitoJUnitRunner.class)
public class DemoTest {
 @Spy
 private SomeService service = new RealServiceImpl();

 @InjectMocks
 private Demo demo;

 /* ... */
}
</code></pre>

Mockito will consider all fields having <code>@Mock</code> or <code>@Spy</code> annotation as potential candidates to be injected into the instance annotated with <code>@InjectMocks</code> annotation. In the above case <code>'RealServiceImpl'</code> instance will get injected into the 'demo'

For more details refer

<a href="http://site.mockito.org/" rel="noreferrer">Mockito-home</a>

<a href="https://static.javadoc.io/org.mockito/mockito-core/2.18.3/org/mockito/Spy.html" rel="noreferrer">@Spy</a>

<a href="https://static.javadoc.io/org.mockito/mockito-core/2.18.3/org/mockito/Mock.html" rel="noreferrer">@Mock</a>

blocks|key|171017|text|除了@Dev空白答案之外，如果您想使用Spring创建的现有bean，则可以将代码修改为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|171018|@RunWith(MockitoJUnitRunner.class)
public+class+DemoTest+{

++++@Inject
++++private+ApplicationContext+ctx;

++++@Spy
++++private+SomeService+service;

++++@InjectMocks
++++private+Demo+demo;

++++@Before
++++public+void+setUp(){
++++++++service+=+ctx.getBean(SomeService.class);
++++}

++++/*+...+*/
}|code-block|syntax|javascript|171019|这样，您不需要更改代码(添加另一个构造函数)就可以使测试正常工作。|171020|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In Addition to @Dev Blanked answer, if you want to use an existing bean that was created by Spring the code can be modified to:

<pre><code>@RunWith(MockitoJUnitRunner.class)
public class DemoTest {

 @Inject
 private ApplicationContext ctx;

 @Spy
 private SomeService service;

 @InjectMocks
 private Demo demo;

 @Before
 public void setUp(){
 service = ctx.getBean(SomeService.class);
 }

 /* ... */
}
</code></pre>

This way you don't need to change your code (add another constructor) just to make the tests work.

blocks|key|171049|text|Mockito不是DI框架，甚至DI框架也鼓励构造函数注入而不是字段注入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|171050|因此，您只需声明一个构造函数来设置被测类的依赖关系：|171051|@Mock
private+SomeService+serviceMock;

private+Demo+demo;

/*+...+*/
@BeforeEach
public+void+beforeEach(){
+++demo+=+new+Demo(serviceMock);
}|code-block|syntax|javascript|171052|在一般情况下使用Mockito+spy是一个糟糕的建议。这使得测试类变得脆弱、不整洁、容易出错:什么才是真正被嘲笑的？真正测试的是什么？|offset|length|style|CODE|171053|@InjectMocks和@Spy也损害了整体设计，因为它鼓励臃肿的类和类中的混合责任。|171054|请在盲目使用之前使用read+the+spy()+javadoc+(不是我的重点)：|171055|171056|创建了一个真实对象的间谍。间谍调用真正的方法，除非它们被存根。真正的间谍应该小心使用，偶尔使用，例如在处理遗留代码时。|blockquote|BOLD|171057|171058|像往常一样，您将阅读partial+mock+warning：面向对象编程通过将复杂性划分为单独的、特定的SRPy对象来处理复杂性。partial+mock如何适应这种范式？它就是不..。部分模拟通常意味着复杂性已移动到同一对象上的不同方法。在大多数情况下，这不是您想要的设计应用程序的方式。|171059|然而，在极少数情况下，部分mock会派上用场:处理你不能轻易更改的代码(第三方接口，遗留代码的临时重构等)。但是，对于新的、测试驱动的和设计良好的代码，我不会使用部分模拟。|171060|entityMap|0|LINK|mutability|MUTABLE|url|https://static.javadoc.io/org.mockito/mockito-core/3.0.0/org/mockito/Mockito.html#spy-T-^0|0|0|0|G|3|0|0|C|D|4|0|J|5|A|M|0|0|0|H|3|16|5|0|0|A|K|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1D|8|@$K|1E|L|1F|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1G|8|@$K|1H|L|1I|M|N]|$K|1J|L|1K|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1L|8|@$K|1M|L|1N|M|N]]|9|@$K|1O|L|1P|1|1Q]]|A|$]]|$1|S|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|1S|8|@$K|1T|L|1U|M|W]|$K|1V|L|1W|M|W]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Y|8|@$K|1Z|L|20|M|N]]|9|@]|A|$]]|$1|10|3|11|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Mockito is not a DI framework and even DI frameworks encourage constructor injections over field injections. 
So you just declare a constructor to set dependencies of the class under test :

<pre><code>@Mock
private SomeService serviceMock;

private Demo demo;

/* ... */
@BeforeEach
public void beforeEach(){
 demo = new Demo(serviceMock);
}
</code></pre>

Using Mockito <code>spy</code> for the general case is a terrible advise. It makes the test class brittle, not straight and error prone : What is really mocked ? What is really tested ? 
<code>@InjectMocks</code> and <code>@Spy</code> also hurts the overall design since it encourages bloated classes and mixed responsibilities in the classes. 
Please <a href="https://static.javadoc.io/org.mockito/mockito-core/3.0.0/org/mockito/Mockito.html#spy-T-" rel="noreferrer">read the <code>spy()</code> javadoc</a> before using that blindly (emphasis is not mine) : 

<blockquote>
 Creates a spy of the real object. The spy calls real methods unless
 they are stubbed. Real spies should be used carefully and
 occasionally, for example when dealing with legacy code.
 
 As usual you are going to read the <code>partial mock warning</code>: Object
 oriented programming tackles complexity by dividing the complexity
 into separate, specific, SRPy objects. How does partial mock fit into
 this paradigm? Well, it just doesn't... Partial mock usually means
 that the complexity has been moved to a different method on the same
 object. In most cases, this is not the way you want to design your
 application.
 
 However, there are rare cases when partial mocks come handy: dealing
 with code you cannot change easily (3rd party interfaces, interim
 refactoring of legacy code etc.) However, I wouldn't use partial mocks
 for new, test-driven &amp; well-designed code.
</blockquote>

blocks|key|2767837|text|我知道这是一个老问题，但我们在尝试注入Strings时也面临着同样的问题。因此，我们发明了一个JUnit5/Mockito扩展，它可以做您想要的事情：https://github.com/exabrial/mockito-object-injection|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2767838|编辑：|2767839|@InjectionMap
+private+Map<String,+Object>+injectionMap+=+new+HashMap<>();

+@BeforeEach
+public+void+beforeEach()+throws+Exception+{
++injectionMap.put("securityEnabled",+Boolean.TRUE);
+}

+@AfterEach
+public+void+afterEach()+throws+Exception+{
++injectionMap.clear();
+}|code-block|syntax|javascript|2767840|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/exabrial/mockito-object-injection^0|23|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

I know this is an old question, but we were faced with the same problem when trying to inject Strings. So we invented a JUnit5/Mockito extension that does exactly what you want: <a href="https://github.com/exabrial/mockito-object-injection" rel="nofollow noreferrer">https://github.com/exabrial/mockito-object-injection</a>

EDIT:

<pre><code>@InjectionMap
 private Map&lt;String, Object&gt; injectionMap = new HashMap&lt;&gt;();

 @BeforeEach
 public void beforeEach() throws Exception {
 injectionMap.put("securityEnabled", Boolean.TRUE);
 }

 @AfterEach
 public void afterEach() throws Exception {
 injectionMap.clear();
 }
</code></pre>

blocks|key|167394|text|在Spring中，有一个名为ReflectionTestUtils的专用实用程序用于此目的。获取特定实例并将其注入到字段中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|167395|@Spy
..
@Mock
..

@InjectMock
Foo+foo;

@BeforeEach
void+_before(){
+++ReflectionTestUtils.setField(foo,"bar",+new+BarImpl());//+`bar`+is+private+field
}|code-block|syntax|javascript|167396|entityMap^0|E|J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

In Spring there is a dedicated utility called <code>ReflectionTestUtils</code> for this purpose. Take the specific instance and inject into the the field.

<pre class="lang-java prettyprint-override"><code>
@Spy
..
@Mock
..

@InjectMock
Foo foo;

@BeforeEach
void _before(){
 ReflectionTestUtils.setField(foo,"bar", new BarImpl());// `bar` is private field
}
</code></pre>

I'm using Mockito's <code>@Mock</code> and <code>@InjectMocks</code> annotations to inject dependencies into private fields which are annotated with Spring's <code>@Autowired</code>:

<pre><code>@RunWith(MockitoJUnitRunner.class)
public class DemoTest {
 @Mock
 private SomeService service;

 @InjectMocks
 private Demo demo;

 /* ... */
}
</code></pre>

and

<pre><code>public class Demo {

 @Autowired
 private SomeService service;

 /* ... */
}
</code></pre>

Now I would like to also inject real objects into private <code>@Autowired</code> fields (without setters). Is this possible or is the mechanism limited to injecting Mocks only?

Mockito: Inject real objects into private @Autowired fields

我正在使用Mockito的@Mock和@InjectMocks注解将依赖项注入到用Spring的@Autowired注解的私有字段中@RunWith(MockitoJUnitRunner.class)public class DemoTest {    @Mock    private SomeService serv...

问Mockito:将真实对象注入到private @Autowired字段中
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mockito:将真实对象注入到private @Autowired字段中EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mockito:将真实对象注入到private @Autowired字段中
EN