blocks|key|1238581|text|更新到2019.2.2或更高版本，其中包含相关问题的修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1238582|解决方法是使用IntelliJ思想而不是通过更改委托选项来运行测试。|1238583|entityMap|0|LINK|mutability|MUTABLE|url|https://blog.jetbrains.com/idea/2019/09/intellij-idea-2019-2-2-is-here/|1|https://youtrack.jetbrains.com/issue/IDEA-221159|2|https://i.imgur.com/HpeUaUE.png^0|3|8|0|L|4|1|0|O|4|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

Update to <a href="https://blog.jetbrains.com/idea/2019/09/intellij-idea-2019-2-2-is-here/" rel="noreferrer">2019.2.2</a> or later, which contains the fix for the <a href="https://youtrack.jetbrains.com/issue/IDEA-221159" rel="noreferrer">related issue</a>.

A workaround is to run the tests using IntelliJ IDEA instead of Gradle by changing the <a href="https://i.imgur.com/HpeUaUE.png" rel="noreferrer">delegation option</a>.

blocks|key|2678966|text|对于那些还在面对这一切的人来说-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2678967|检查Build选项卡中是否有编译器错误。|offset|length|style|CODE|2678968|entityMap^0|0|2|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For anyone that is still facing this - 
check if you have any compiler errors in the <code>Build</code> tab.

blocks|key|2678970|text|在我的例子中，我有一个无效的Gradle+JVM配置(配置的jdk已从文件系统中删除)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2678971|为了解决这个问题，它必须更改文件->设置中的->构建、执行、部署->构建工具->+Gradle+->+Gradle+JVM。|2678972|由于一个无效的JDK路径，它是红色的。|2678973|IntelliJ版本:+2019.2.3|2678974|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

In my case I had an invalid Gradle JVM configuration (configured jdk was removed from filesystem).
To Fix it had to change Gradle JVM on File -&gt; Settings -&gt; Build, Execution, Deployment -&gt; Build Tools -&gt; Gradle -&gt; Gradle JVM.
It was red due to an invalid JDK path.
IntelliJ version: 2019.2.3

blocks|key|2048736|text|对我来说，同样的问题正在发生，下面的变化对我来说是有效的。我正在使用的IntelliJ版本:+2019.2.2|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048737|在IntelliJ+IDE中，转到|2048738|文件->设置->Build，执行，部署->构建工具->+Gradle|2048739|在Run+test+using:下拉菜单中，选中的选项是：Gradle(default)将其更改为IntelliJ+IDEA|offset|length|style|CODE|2048740|​|2048741|📷|atomic|2048742|2048743|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/43f420de76d2261e463ca9d3cc846450.png|imageAlt^0|0|0|0|1|F|T|F|1D|D|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@$H|14|I|15|J|K]|$H|16|I|17|J|K]|$H|18|I|19|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1B|8|@]|9|@$H|1C|I|1D|1|1E]]|A|$]]|$1|Q|3|M|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]]]

For me, the Same issue was occurring, below changes worked for me.
IntelliJ Version I am using: 2019.2.2 
In IntelliJ IDE, Go to 

File -> Settings ->Build,Execution, Deployment -> Build Tools -> Gradle

here in the <code>Run test using:</code> dropdown selected option was: <code>Gradle(default)</code> changed it to <code>IntelliJ IDEA</code>

<a href="https://i.stack.imgur.com/ef4Jf.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ef4Jf.png" alt=""></a>

blocks|key|2048776|text|我使用的是同样的问题，甚至使用IntelliJ+IDEA+2019.2.4+(顶部回答说这是在2019.2.2)。结果发现我在尝试之前必须先做Invalidate+Caches+/+Restart...。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2048777|entityMap^0|1Z|U|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I was using facing the same issue even using IntelliJ IDEA 2019.2.4 (top answer said this was fixed on 2019.2.2). Turns out I had to <code>Invalidate Caches / Restart...</code> before trying.

blocks|key|2679038|text|当我试图为自己解决这个问题时，我发现JUnit+4有效，但是JUnit+5报告“测试没有收到”。根据petrikainulainen.net，我找到了我的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2679039|尽管Gradle+4.6+(显然所有较新版本)对JUnit+5都有本机支持，但默认情况下不启用这种支持。如果我们想要启用它，我们必须确保测试任务使用JUnit+5而不是JUnit+4。|blockquote|2679040|当我向Gradle添加以下代码时，JUnit+5起了作用。|2679041|test+{
++++useJUnitPlatform()
}|code-block|syntax|javascript|2679042|entityMap|0|LINK|mutability|MUTABLE|url|https://www.petrikainulainen.net/programming/testing/junit-5-tutorial-running-unit-tests-with-gradle/^0|1E|K|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|C|$]]|$1|I|3|J|5|K|7|11|8|@]|9|@]|C|$L|M]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

When trying to work out this problem for myself, I discovered JUnit 4 worked, but JUnit 5 reports "Tests were not received." Per <a href="https://www.petrikainulainen.net/programming/testing/junit-5-tutorial-running-unit-tests-with-gradle/" rel="noreferrer">petrikainulainen.net</a> I found my solution.

<blockquote>
 Even though Gradle 4.6 (and obviously all newer versions) has a native
 support for JUnit 5, this support is not enabled by default. If we
 want to enable it, we have to ensure that the test task uses JUnit 5
 instead of JUnit 4.
</blockquote>

When I added the following code to Gradle, JUnit 5 worked.

<pre><code>test {
 useJUnitPlatform()
}
</code></pre>

blocks|key|2048813|text|对于我来说，点击“帮助->检查更新.”是有帮助的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048814|Help+->+Check+for+Updates...|offset|length|2048815|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/YdMk5.jpg%2529^0|0|0|S|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

For me, this is helpful to click "Help -> Check for Updates..."

<a href="https://i.stack.imgur.com/YdMk5.jpg)" rel="nofollow noreferrer">Help -> Check for Updates...</a>

blocks|key|2679079|text|当我同时使用以下两种插件时，出现了问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2679080|plugins
{
++id+'org.springframework.boot'+version+'2.2.6.RELEASE'
++id+'io.spring.dependency-management'+version+'1.0.7.RELEASE'
++...
}|code-block|syntax|javascript|2679081|删除第二个测试后，查找并执行测试。|2679082|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|$]]

The problem occurred as I used both following plugins at the same time

<pre><code>plugins
{
 id 'org.springframework.boot' version '2.2.6.RELEASE'
 id 'io.spring.dependency-management' version '1.0.7.RELEASE'
 ...
}
</code></pre>

after deletion of the second one, the tests were found and executed.

blocks|key|2679129|text|我经常不得不删除生成和输出文件夹来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2679130|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I often have to delete build and out folder to fix this problem ..

blocks|key|1238744|text|您最喜欢的方法不是告诉系统如何运行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1238745|例如，在类头上定义这样的测试运行程序：|1238746|@RunWith(MockitoJUnitRunner::class)
class+MYTest+{//...}|code-block|syntax|javascript|1238747|或者可以定义junitX运行程序等|1238748|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

your most likey not tellinig the system how to run the tests.
on your class header define a test runner like this for example:
<pre><code>@RunWith(MockitoJUnitRunner::class)
class MYTest {//...}
</code></pre>
or can define junitX runner , etc

blocks|key|1238776|text|对于那些使用IntelliJ+&Kotlin仍有此问题的人：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1238777|将以下行添加到build.grade.kts中。我希望这对你们中的一些人有帮助。|1238778|dependencies+{
++++testImplementation(kotlin("test-junit5"))
++++testImplementation(platform("org.junit:junit-bom:5.7.0"))
++++testImplementation("org.junit.jupiter:junit-jupiter")}
tasks.test+{
++++useJUnitPlatform()
++++testLogging+{
++++++++events("passed",+"skipped",+"failed")
++++}
}|code-block|syntax|javascript|1238779|PS:不添加“任务”。在测试{.}之前，我得到了以下错误！|1238780|找不到调用()函数|blockquote|1238781|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|T|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|O|$]]

For those who still might have this problem using IntelliJ &amp; Kotlin:
Add the following lines to the build.grade.kts.
I hope it helps some of you.
<pre><code>dependencies {
 testImplementation(kotlin(&quot;test-junit5&quot;))
 testImplementation(platform(&quot;org.junit:junit-bom:5.7.0&quot;))
 testImplementation(&quot;org.junit.jupiter:junit-jupiter&quot;)}
tasks.test {
 useJUnitPlatform()
 testLogging {
 events(&quot;passed&quot;, &quot;skipped&quot;, &quot;failed&quot;)
 }
}
</code></pre>
PS: without adding the &quot;task.&quot; before test{...} I was getting the following error!
<blockquote>
the function invoke() is not found
</blockquote>

blocks|key|1238811|text|对于使用IntelliJ的项目，我的问题是Spring当前附带了JUnit+5。我还手动安装了JUnit+5。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1238812|在删除了compile+'org.junit.jupiter:junit-jupiter-api:5.6.3'中的build.gradle之后，我的测试又开始工作了。|offset|length|style|CODE|1238813|entityMap^0|0|4|1F|1L|C|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

For a Spring boot, gradle project using IntelliJ, my issue was that Spring Boot currently brings JUnit 5 with it. I had also manually installed JUnit 5 as well.
After deleting <code>compile 'org.junit.jupiter:junit-jupiter-api:5.6.3'</code> in <code>build.gradle</code> my tests began to work again.

blocks|key|2048890|text|确保您正在使用来自org.junit.Test的正确@Test注释；有时，在自动导入时，它可以从其他库获得注释。前org.junit.jupiter.api.Test；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048891|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

make sure you are using the correct @Test annotation which is from org.junit.Test;
Sometimes while auto importing it can get the annotation from some other library. for ex - org.junit.jupiter.api.Test;

blocks|key|2048907|text|试着添加|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048908|testRuntimeOnly("org.junit.vintage:junit-vintage-engine:5.7.2")|code-block|syntax|javascript|2048909|如果您的测试使用旧的org.junit.Test而不是org.junit.jupiter.api.Test|offset|length|style|CODE|2048910|entityMap^0|0|0|A|E|R|Q|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Try add
<pre><code>testRuntimeOnly(&quot;org.junit.vintage:junit-vintage-engine:5.7.2&quot;)
</code></pre>
if your tests use the older <code>org.junit.Test</code> instead of <code>org.junit.jupiter.api.Test</code>

blocks|key|2679330|text|这是对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2679331|File+->+Settings+->+Build,+Execution,+Deployment+->+Build+Tools+->+Gradle

Switching+Gradle+JVM+to:+JAVA_HOME+version+11.0.10+worked.+|code-block|syntax|javascript|2679332|在它成为Project+SDK之前。|2679333|📷|atomic|offset|length|2679334|​|2679335|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/b464192c9a97b18ed224d29050cf0128.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|11|8|@]|9|@$L|12|M|13|1|14]]|A|$]]|$1|N|3|O|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

This is the solution worked for me:
<pre><code>File -&gt; Settings -&gt; Build, Execution, Deployment -&gt; Build Tools -&gt; Gradle

Switching Gradle JVM to: JAVA_HOME version 11.0.10 worked. 
</code></pre>
Before it was Project SDK.
<a href="https://i.stack.imgur.com/edvO3.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/edvO3.png" alt="enter image description here" /></a>

blocks|key|2679357|text|我遇到了这个问题，结果发现我在一个为JUnit+5配置的模块中编写了JUnit+4测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2679358|import+org.junit.jupiter.api.Assertions.*
import+org.junit.jupiter.api.Test|code-block|syntax|javascript|2679359|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I ran into this issue and it turned out that I had written JUnit 4 tests in a module that was configured for JUnit 5. The solution was to use JUnit 5 imports in my test class:
<pre><code>import org.junit.jupiter.api.Assertions.*
import org.junit.jupiter.api.Test
</code></pre>

blocks|key|2679387|text|对我来说，“重置”等级设置起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2679388|​|2679389|📷|atomic|offset|length|2679390|2679391|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/d690562d923464ac1e2f401919330a05.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

For me 'resetting' the Gradle setting worked.
<a href="https://i.stack.imgur.com/k8Wyu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/k8Wyu.png" alt="enter image description here" /></a>

blocks|key|1239059|text|如果您使用Kotlin+DSL作为您的gradle脚本，那么添加以下内容对我来说是个窍门：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1239060|tasks.withType<Test>+{
++++useJUnitPlatform()+//+Make+all+tests+use+JUnit+5
}|code-block|syntax|javascript|1239061|说明:以上习惯Kotlin使所有任务类型测试使用JUnit+5平台，这是测试工作所必需的。|1239062|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|$]]

If you are using Kotlin DSL as your gradle script then adding the following did the trick for me:
<pre><code>tasks.withType&lt;Test&gt; {
 useJUnitPlatform() // Make all tests use JUnit 5
}
</code></pre>
Explanation: Above idiomatic Kotlin DSL makes all tasks with type Test to use JUnit 5 platform which is required for test to work.

blocks|key|1239131|text|我也在挣扎，我在网上找不到答案，我最终意识到这是由于一个System.exit(0)电话。因此，所有测试都会在调用退出调用的任何代码之后静默停止，并在IntelliJ中将该测试显示为“忽略”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1239132|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was also struggling, and no answer online I found worked for me, and I eventually realized it was due to a System.exit(0) call. As a result, all tests would silently stop after calling whatever code with the exit call and show that test as &quot;ignored&quot; in IntelliJ.

blocks|key|1239149|text|对于Junit+5测试，将其添加到应用程序级build.gradle文件中的android{}块下。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1239150|testOptions+{
++++unitTests+{
++++++++all+{
++++++++++++useJUnitPlatform()
++++++++}
++++}
}|code-block|syntax|javascript|1239151|entityMap^0|M|C|12|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

For Junit 5 tests add this in your app-level <code>build.gradle</code> file under <code>android{}</code> block.
<pre><code>testOptions {
 unitTests {
 all {
 useJUnitPlatform()
 }
 }
}
</code></pre>

blocks|key|2049165|text|在我的例子中，Gradle脱机模式在Android上处于活动状态。刚把离线切换到网上，它就开始工作了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2049166|entityMap^0|7|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case Gradle offline mode was active on Android studio. Just toggled the offline to online and it started working.

I have a Kotlin project and when I run my JUnit tests, I can't see tests execution result in IntelliJ and get this message instead: 

<blockquote>
 test events were not received
</blockquote>

I'm using this setup:

<pre><code>macOS Mojave

Intellij CE 2019.2

JDK 11.0.3

Kotlin 1.3.50

Gradle 5.2.1

JUnit 4.12
</code></pre>

Can you help me?

"Test events were not received" when run tests using Intellij

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个Kotlin项目，当我运行我的JUnit测试时，我无法在IntelliJ中看到测试执行结果，而是得到以下消息：未收到测试事件我正在使用这个设置：macOS MojaveIntellij CE 2019.2JDK 11.0.3Kotlin 1.3.50Gradle 5.2.1JUnit 4.12你能帮帮我吗?

问使用Intellij运行测试时，“未收到测试事件”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Intellij运行测试时，“未收到测试事件”EN