IntelliJ 2017中运行JUnit测试失败，是否是包结构错误？

Hey there! Let's figure out why your JUnit tests aren't running in IntelliJ 2017—more often than not, it's a small issue with the test structure or setup. I'll walk you through the correct structure and key checks to validate your setup.

First, make sure your tests are placed in the right spot—IntelliJ relies on standard conventions to recognize test classes:

• Tests should live in the src/test/java directory, mirroring the package structure of your main code in src/main/java. For example:
  • Main class: com.example.MyService → src/main/java/com/example/MyService.java
  • Test class: com.example.MyServiceTest → src/test/java/com/example/MyServiceTest.java
• If src/test/java doesn’t exist or isn’t marked as a test source root, right-click the directory → Mark Directory as → Test Sources Root. This tells IntelliJ to treat files here as tests.

Let’s use JUnit 4 (the most widely supported version in IntelliJ 2017) as an example—adjust if you’re using JUnit 5 (note the different annotations):

package com.example; // Must match the package of your main class

import org.junit.Test; // JUnit 4 annotation; use org.junit.jupiter.api.Test for JUnit 5
import static org.junit.Assert.assertEquals; // Static import for assertions

public class MyServiceTest {

    // Test methods must be public, have no return value, no parameters
    @Test
    public void testAddition() {
        // Initialize the class you're testing
        MyService service = new MyService();
        
        // Execute the method to test
        int result = service.add(2, 3);
        
        // Verify the result matches your expectation
        assertEquals(5, result);
    }

    // You can have multiple test methods, each annotated with @Test
    @Test
    public void testMultiplication() {
        MyService service = new MyService();
        int result = service.multiply(4, 5);
        assertEquals(20, result);
    }
}

Even with the right structure, these setup details can break test execution:

• Check JUnit Dependencies: Ensure your build file (Maven/Gradle) includes the correct JUnit dependency.
  For Maven (pom.xml):

  <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>4.12</version>
      <scope>test</scope>
  </dependency>
  

  For Gradle (build.gradle):

  testImplementation 'junit:junit:4.12'
  

  If you’re not using a build tool, manually add JUnit libraries via File → Project Structure → Libraries → + and select the JUnit JAR files.
• Verify Test Recognition: You should see a green run icon next to your test class and method names. If not, double-check the directory is marked as a test root, and you’re using the correct annotation for your JUnit version.
• Run Tests Correctly: Right-click a test method → Run 'testAddition', or right-click the test class → Run 'MyServiceTest'. Avoid running tests from the main code directory.

• Wrong Annotation: Mixing JUnit 4 and JUnit 5 annotations (e.g., using org.junit.jupiter.api.Test with JUnit 4 dependencies) will prevent IntelliJ from detecting tests.
• Non-Public Test Methods: Test methods must be public—private or package-private methods won’t be executed.
• Tests in Main Directory: If your test class is in src/main/java, IntelliJ won’t treat it as a test. Move it to src/test/java.

If you’ve checked all these and still can’t run tests, feel free to share a snippet of your project structure or test code, and we can dig deeper.

内容的提问来源于stack exchange，提问作者Leia_Organa