Testing Mastery: JUnit, Mockito & Integration Tests · 课时

设置集成测试

配置项目以支持集成测试，包括管理测试环境和依赖项。

设置集成测试 是 CoddyKit 上的免费 Testing Mastery: JUnit, Mockito & Integration Tests 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Testing Mastery: JUnit, Mockito & Integration Tests 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Testing Mastery: JUnit, Mockito & Integration Tests 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Integration Test Setup Intro

Welcome to setting up Integration Tests! After learning about the difference between unit and integration tests, it's time to prepare our project.

Proper setup is crucial for integration tests to run reliably. It ensures your tests are isolated, repeatable, and don't interfere with your development environment.

Separate Source Folders

The first step is to clearly separate your integration tests from your unit tests. This helps organize your codebase and allows build tools to treat them differently.

Unit Tests: Typically reside in src/test/java.
Integration Tests: Often placed in a dedicated folder like src/it/java or src/integrationTest/java.

This separation makes it easier to run them at different stages of your build process.

Maven: Configure IT Sources

If you're using Maven, you need to tell your pom.xml to recognize the new integration test source folder. The build-helper-maven-plugin is commonly used for this.

It adds src/it/java as a test source directory, allowing Maven to compile your integration tests.

<project>
  ...
  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>build-helper-maven-plugin</artifactId>
        <version>3.5.0</version>
        <executions>
          <execution>
            <id>add-integration-test-sources</id>
            <phase>generate-test-sources</phase>
            <goals>
              <goal>add-test-source</goal>
            </goals>
            <configuration>
              <sources>
                <source>src/it/java</source>
              </sources>
            </configuration>
          </execution>
        </executions>
      </plugin>
      ...
    </plugins>
  </build>
</project>

Gradle: Configure IT Sources

For Gradle users, defining a separate source set for integration tests is straightforward. This allows you to compile and run integration tests independently.

The example below shows how to define an integrationTest source set and configure its dependencies.

sourceSets {
    integrationTest {
        java.srcDir 'src/it/java'
        resources.srcDir 'src/it/resources'
        compileClasspath += sourceSets.main.output
        runtimeClasspath += sourceSets.main.output
    }
}

configurations {
    integrationTestImplementation.extendsFrom testImplementation
    integrationTestRuntimeOnly.extendsFrom testRuntimeOnly
}

task integrationTest(type: Test) {
    testClassesDirs = sourceSets.integrationTest.output.classesDirs
    classpath = sourceSets.integrationTest.runtimeClasspath
    shouldRunAfter test
}

check.dependsOn integrationTest

Essential Test Dependencies

Integration tests often require specific dependencies that unit tests might not. These can include:

In-memory databases: Like H2 or HSQLDB for fast, isolated database testing.
Testcontainers: A library to spin up real service containers (databases, message queues) in Docker.
Web testing frameworks: For testing web layers (e.g., Spring's spring-test, MockMvc).

Add these to your test or integration test dependency scope.

Maven Failsafe Plugin

While Maven's Surefire plugin runs unit tests, the Maven Failsafe Plugin is designed for integration tests.

It executes tests during the integration-test and verify phases, ensuring that any setup (like starting a server) happens before tests run and teardown occurs afterward.

<project>
  ...
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-failsafe-plugin</artifactId>
        <version>3.2.5</version>
        <executions>
          <execution>
            <goals>
              <goal>integration-test</goal>
              <goal>verify</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      ...
    </plugins>
  </build>
</project>

Dedicated Test Configuration

Integration tests often need a different configuration than your main application or unit tests. For example, they might connect to a specific test database or use different external service URLs.

It's good practice to use separate configuration files (e.g., application-it.properties for Spring Boot) that override default settings during integration test execution.

Preparing the Test Environment

Before integration tests run, you often need to prepare the environment. This could involve:

Starting an embedded database.
Spinning up Docker containers for external services using Testcontainers.
Initializing specific test data.

JUnit's @BeforeAll and @AfterAll annotations are perfect for setting up and tearing down resources once per test class.

Environment Setup Example

Here's a simple example demonstrating how you might use @BeforeAll to 'prepare' a resource for your integration tests. This setup runs once before all tests in the class.

Try running this example to see the setup message.

import org.junit.jupiter.api.AfterAll;
import org.junit.jupiter.api.BeforeAll;
import org.junit.jupiter.api.Test;

public class SimpleIntegrationSetupTest {

    @BeforeAll
    static void setupEnvironment() {
        System.out.println("--- Setting up test environment (e.g., starting a database) ---");
        // In a real scenario, you'd start a container or connect to a test DB here.
    }

    @AfterAll
    static void tearDownEnvironment() {
        System.out.println("--- Tearing down test environment (e.g., stopping a database) ---");
        // In a real scenario, you'd stop containers or clean up resources here.
    }

    @Test
    void testSomethingIntegrated() {
        System.out.println("  Running an integration test...");
        // Your actual integration test logic would go here.
        // assert something...
    }

    public static void main(String[] args) {
        // This main method allows the snippet to be runnable.
        // In a real project, tests are run by build tools.
        System.out.println("This is a placeholder for running the test.");
        // You would typically use JUnit's API to run tests programmatically if not using Maven/Gradle.
    }
}

Running ITs Question

You've set up your project for integration tests using Maven. Which Maven command is typically used to execute these tests using the Failsafe plugin?

Recap: Structured Testing

Great job! You've learned how to set up your project for integration tests.

We separate integration tests into their own source folders (e.g., src/it/java).
Build tools like Maven (with build-helper-maven-plugin and maven-failsafe-plugin) or Gradle are configured to recognize and run them.
Specific dependencies and dedicated configuration files ensure isolated test environments.
@BeforeAll and @AfterAll help manage resource setup and teardown.

This robust setup provides a solid foundation for writing effective integration tests!

常见问题解答

「设置集成测试」课时是免费的吗？

是的 — 「设置集成测试」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Testing Mastery: JUnit, Mockito & Integration Tests 课程的其余内容，请升级到 CoddyKit PRO。 Testing Mastery: JUnit, Mockito & Integration Tests 课程共包含 4 节课。

「设置集成测试」这节课中我会学到什么？

配置项目以支持集成测试，包括管理测试环境和依赖项。你通过在浏览器中直接运行的动手代码来练习 Testing Mastery: JUnit, Mockito & Integration Tests，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Testing Mastery: JUnit, Mockito & Integration Tests 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Testing Mastery: JUnit, Mockito & Integration Tests 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「设置集成测试」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Testing Mastery: JUnit, Mockito & Integration Tests 课中编写并运行代码吗？

能。每节 Testing Mastery: JUnit, Mockito & Integration Tests 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Testing Mastery: JUnit, Mockito & Integration Tests