통합 테스트 설정
테스트 환경과 의존성 관리를 포함해 프로젝트에서 통합 테스트를 지원하도록 구성합니다.
통합 테스트 설정은(는) CoddyKit의 무료 Testing Mastery: JUnit, Mockito & Integration Tests 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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/javaorsrc/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 integrationTestEssential 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-pluginandmaven-failsafe-plugin) or Gradle are configured to recognize and run them. - Specific dependencies and dedicated configuration files ensure isolated test environments.
@BeforeAlland@AfterAllhelp manage resource setup and teardown.
This robust setup provides a solid foundation for writing effective integration tests!
자주 묻는 질문
“통합 테스트 설정” 강의는 무료인가요?
네 — “통합 테스트 설정” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Testing Mastery: JUnit, Mockito & Integration Tests 강의 전체를 잠금 해제할 수 있습니다. Testing Mastery: JUnit, Mockito & Integration Tests 강의에는 총 4개의 강의가 포함되어 있습니다.
“통합 테스트 설정”에서 뭘 배우나요?
테스트 환경과 의존성 관리를 포함해 프로젝트에서 통합 테스트를 지원하도록 구성합니다. 브라우저에서 직접 실행하는 실습 코드로 Testing Mastery: JUnit, Mockito & Integration Tests을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Testing Mastery: JUnit, Mockito & Integration Tests을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Testing Mastery: JUnit, Mockito & Integration Tests은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“통합 테스트 설정” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Testing Mastery: JUnit, Mockito & Integration Tests 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Testing Mastery: JUnit, Mockito & Integration Tests 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.