0Pricing
Testing Mastery: JUnit, Mockito & Integration Tests · レッスン

結合テストのセットアップ

テスト環境と依存関係の管理を含め、結合テストを実行できるようプロジェクトを構成します。

「結合テストのセットアップ」はCoddyKit上の無料Testing Mastery: JUnit, Mockito & Integration Testsレッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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!

よくある質問

「結合テストのセットアップ」レッスンは無料ですか？

はい。「結合テストのセットアップ」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Testing Mastery: JUnit, Mockito & Integration Testsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Testing Mastery: JUnit, Mockito & Integration Testsコースには全4レッスンが含まれています。

「結合テストのセットアップ」で何を学びますか？

テスト環境と依存関係の管理を含め、結合テストを実行できるようプロジェクトを構成します。 ブラウザで直接実行するハンズオンコードでTesting Mastery: JUnit, Mockito & Integration Testsを演習し、24時間対応の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フィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. 単体テストと結合テストの違い
  2. 結合テストのセットアップ
  3. データベース連携のテスト
  4. WireMockによる外部APIのテスト
← Testing Mastery: JUnit, Mockito & Integration Testsに戻る