blocks|key|1967026|text|问题是，来自Hamcrest和Mockito的静态导入具有相似的名称，但分别返回匹配器和实际值。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1967027|一种解决办法是简单地复制Hamcrest和/或Mockito类，并删除/重命名静态函数，以便它们更容易记住，并且在自动完成中显示得更少。我就是这么做的。|1967028|此外，在使用assertions时，我尽量避免使用assertThat，而使用其他mock和verify，例如|style|CODE|1967029|assertEquals(1,+1);
verify(someMock).someMethod(eq(1));|code-block|syntax|javascript|1967030|而不是|1967031|assertThat(1,+equalTo(1));
verify(someMock).someMethod(eq(1));|1967032|如果你从你的收藏夹中删除类，并输入长名称，例如org.hamcrest.Matchers.equalTo，然后执行CTRL%2BSHIFT%2BM到'Add+Import‘，那么autocomplete只会显示Hamcrest匹配器，而不是任何Mockito匹配器。只要你不混用匹配器，你就可以用另一种方式来做。|1967033|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/hamcrest/^0|6|8|0|0|0|6|A|P|A|1A|6|0|0|0|0|N|T|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@$A|18|B|19|H|I]|$A|1A|B|1B|H|I]|$A|1C|B|1D|H|I]]|9|@]|C|$]]|$1|J|3|K|5|L|7|1E|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|C|$]]|$1|Q|3|R|5|L|7|1G|8|@]|9|@]|C|$M|N]]|$1|S|3|T|5|6|7|1H|8|@$A|1I|B|1J|H|I]]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

The problem is that static imports from <a href="http://code.google.com/p/hamcrest/" rel="noreferrer">Hamcrest</a> and Mockito have similar names, but return Matchers and real values, respectively.

One work-around is to simply copy the Hamcrest and/or Mockito classes and delete/rename the static functions so they are easier to remember and less show up in the auto complete. That's what I did.

Also, when using mocks, I try to avoid <code>assertThat</code> in favor other other <code>assertions</code> and <code>verify</code>, e.g.

<pre><code>assertEquals(1, 1);
verify(someMock).someMethod(eq(1));
</code></pre>

instead of

<pre><code>assertThat(1, equalTo(1));
verify(someMock).someMethod(eq(1));
</code></pre>

If you remove the classes from your Favorites in Eclipse, and type out the long name e.g. <code>org.hamcrest.Matchers.equalTo</code> and do CTRL+SHIFT+M to 'Add Import' then autocomplete will only show you Hamcrest matchers, not any Mockito matchers. And you can do this the other way so long as you don't mix matchers.

blocks|key|1753682|text|以下是我一直在做的事情，以应对这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1753683|我在一个新的测试类上使用了全局导入。|1753684|import+static+org.junit.Assert.*;
import+static+org.mockito.Mockito.*;
import+static+org.mockito.Matchers.*;|code-block|syntax|javascript|1753685|当您编写完测试并需要提交时，您只需使用CTRL%2BSHIFT%2BO来组织包。例如，您可能只剩下：|1753686|import+static+org.mockito.Mockito.doThrow;
import+static+org.mockito.Mockito.mock;
import+static+org.mockito.Mockito.verify;
import+static+org.mockito.Mockito.when;
import+static+org.mockito.Matchers.anyString;|1753687|这使您可以编写代码，而不会“卡住”试图找到要导入的正确包。|1753688|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Here's what I've been doing to cope with the situation.

I use global imports on a new test class.

<pre><code>import static org.junit.Assert.*;
import static org.mockito.Mockito.*;
import static org.mockito.Matchers.*;
</code></pre>

When you are finished writing your test and need to commit, you just CTRL+SHIFT+O to organize the packages. For example, you may just be left with:

<pre><code>import static org.mockito.Mockito.doThrow;
import static org.mockito.Mockito.mock;
import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.when;
import static org.mockito.Matchers.anyString;
</code></pre>

This allows you to code away without getting 'stuck' trying to find the correct package to import.

blocks|key|1967114|text|For+is()|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1967115|import+static+org.hamcrest.CoreMatchers.*;|code-block|syntax|javascript|1967116|对于assertThat()|1967117|import+static+org.junit.Assert.*;|1967118|用于when()和verify()|1967119|import+static+org.mockito.Mockito.*;|1967120|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

For is()

<pre><code>import static org.hamcrest.CoreMatchers.*;
</code></pre>

For assertThat()

<pre><code>import static org.junit.Assert.*;
</code></pre>

For when() and verify()

<pre><code>import static org.mockito.Mockito.*;
</code></pre>

blocks|key|1967124|text|我的导入|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1967125|import+static+org.junit.Assert.assertEquals;
import+static+org.mockito.ArgumentMatchers.anyInt;
import+static+org.mockito.Mockito.mock;
import+static+org.mockito.Mockito.when;

import+org.junit.Test;|code-block|syntax|javascript|1967126|而且它是有效的|1967127|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|$]]

My imports
<pre><code>import static org.junit.Assert.assertEquals;
import static org.mockito.ArgumentMatchers.anyInt;
import static org.mockito.Mockito.mock;
import static org.mockito.Mockito.when;

import org.junit.Test;
</code></pre>
And it works

I'm trying to crash through the brick wall between me and Mockito. I've torn my hair out over trying to get correct import static statements for Mockito stuff. You'd think someone would just throw up a table saying that anyInt() comes from org.mockito.Matchers and when() comes from org.mockito.Mockito, etc., but that would be too helpful to newcomers, no?

This sort of thing, especially when mixed in with myriad more import statements ending in asterisks, isn't always very helpful:

<pre><code>import static org.junit.Assert.*;
import static org.mockito.Mockito.*;
</code></pre>

Yes, I know about and have been trying to use the Eclipse Window -> Preferences-> Java -> Editor-> Content Assist -> Favorites mechanism. It helps, but it doesn't hit the nail on the head.

Any answers to this question would be appreciated.

Many thanks,
Russ

Finding import static statements for Mockito constructs

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想撞穿我和莫基托之间的砖墙。我已经竭尽全力为Mockito的东西获取正确的导入静态语句。你可能认为有人会抛出一张表，说anyInt()来自org.mockito.Matchers，而when()来自org.mockito.Mockito，等等，但这对新手来说太有帮助了，不是吗？这类事情，特别是当与无数以星号结尾的导入...

问查找Mockito构造的导入静态语句
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找Mockito构造的导入静态语句EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找Mockito构造的导入静态语句
EN