계층별 테스트 전략
클린 아키텍처의 모든 계층에서 단위, 통합, 엔드투엔드 테스트를 아우르는 종합적인 테스트 전략을 개발합니다.
계층별 테스트 전략은(는) CoddyKit의 무료 Clean Architecture & Design Patterns in Practice 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Clean Architecture & Design Patterns in Practice 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Clean Architecture & Design Patterns in Practice 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Intro to Layered Testing
Welcome to Layered Testing Strategy! In Clean Architecture, separating concerns allows for a highly effective testing approach.
This lesson explores how to build a comprehensive testing strategy, covering unit, integration, and end-to-end tests across different architectural layers.
The Test Pyramid
A common visualization for testing strategies is the Test Pyramid. It suggests:
- Many small, fast Unit Tests at the base.
- Fewer Integration Tests in the middle.
- Very few, slow End-to-End Tests at the top.
This structure ensures quick feedback and high confidence where it matters most, aligning perfectly with Clean Architecture's decoupled nature.
Unit Tests: Entities
Unit tests are the foundation. In Clean Architecture, we start by testing our Entities. These contain core business rules and should be completely independent of any frameworks or databases.
Focus on testing the pure logic of your entities. They should be fast and deterministic.
public class Product {
private String name;
private double price;
public Product(String name, double price) {
if (name == null || name.trim().isEmpty()) {
throw new IllegalArgumentException("Name invalid.");
}
if (price <= 0) {
throw new IllegalArgumentException("Price must be positive.");
}
this.name = name;
this.price = price;
}
public String getName() { return name; }
public double getPrice() { return price; }
}
public class Main {
public static void main(String[] args) {
try {
Product p = new Product("Book", 25.00);
System.out.println("Product OK: " + p.getName());
} catch (IllegalArgumentException e) {
System.out.println("Error: " + e.getMessage());
}
try {
new Product("Pen", -5.00);
} catch (IllegalArgumentException e) {
System.out.println("Test Failed (expected): " + e.getMessage());
}
}
}Unit Tests: Use Cases
Next, we unit test our Use Cases (Interactors). These encapsulate application-specific business rules. They orchestrate entities and interact with ports (interfaces) to external layers.
When testing use cases, we mock or stub any external dependencies (like repositories or gateways) to isolate the use case's logic.
interface ProductRepository {
void save(String name, double price);
}
class MockProductRepository implements ProductRepository {
private boolean saved = false;
@Override
public void save(String name, double price) {
System.out.println("Mock: Saving " + name + "...");
saved = true;
}
public boolean isSaved() { return saved; }
}
class CreateProductUseCase {
private final ProductRepository repo;
public CreateProductUseCase(ProductRepository repo) {
this.repo = repo;
}
public void execute(String name, double price) {
// Entity validation here in a real app, or trust entity's constructor
repo.save(name, price);
System.out.println("Product creation requested.");
}
}
public class Main {
public static void main(String[] args) {
MockProductRepository mockRepo = new MockProductRepository();
CreateProductUseCase useCase = new CreateProductUseCase(mockRepo);
useCase.execute("Coffee Mug", 15.00);
if (mockRepo.isSaved()) {
System.out.println("Test PASSED: Product saved via mock.");
} else {
System.out.println("Test FAILED: Product not saved.");
}
}
}Integration Tests: Adapters
Integration tests verify the interactions between different components and layers. In Clean Architecture, this often means testing the concrete implementations of our Interface Adapters (e.g., a database repository, an external API gateway) with the actual external systems.
We check if the adapter correctly translates data and interacts with the external service as expected.
Integration Tests: Data Persistence
This type of integration test focuses on the Repository implementations. We ensure they correctly save and retrieve data from the actual database (or an in-memory substitute like H2 for faster tests).
It verifies that your data mapping (e.g., from Entity to DTO) and database queries work as intended.
import java.util.HashMap;
import java.util.Map;
interface ProductRepository {
void save(String id, String name, double price);
String findNameById(String id);
}
class InMemoryProductRepository implements ProductRepository {
private final Map<String, String> products = new HashMap<>(); // id -> name
@Override
public void save(String id, String name, double price) {
products.put(id, name);
System.out.println("In-Memory: Saved " + name + " (ID: " + id + ")");
}
@Override
public String findNameById(String id) {
return products.get(id);
}
}
public class Main {
public static void main(String[] args) {
InMemoryProductRepository repo = new InMemoryProductRepository();
repo.save("P001", "Keyboard", 75.00);
String foundName = repo.findNameById("P001");
if ("Keyboard".equals(foundName)) {
System.out.println("Integration Test PASSED: Keyboard found.");
} else {
System.out.println("Integration Test FAILED: Keyboard not found.");
}
}
}Integration Tests: Presentation Layer
Testing the Presentation Layer (e.g., Controllers, Presenters) involves ensuring they correctly receive requests, call the appropriate use cases, and format responses. We can use mocks for the underlying use cases.
This confirms the API contract and data flow from the external world into your application's use cases.
interface CreateProductUseCase {
void execute(String name, double price);
}
class MockCreateProductUseCase implements CreateProductUseCase {
private boolean called = false;
@Override
public void execute(String name, double price) {
System.out.println("Mock Use Case: Executing for " + name);
called = true;
}
public boolean wasCalled() { return called; }
}
class ProductController {
private final CreateProductUseCase useCase;
public ProductController(CreateProductUseCase useCase) {
this.useCase = useCase;
}
public String createProductEndpoint(String jsonBody) {
// Simulate JSON parsing
String name = jsonBody.contains("name":"Laptop") ? "Laptop" : "Unknown";
double price = jsonBody.contains("price":1200) ? 1200.00 : 0.0;
useCase.execute(name, price);
return "Product creation request received.";
}
}
public class Main {
public static void main(String[] args) {
MockCreateProductUseCase mockUseCase = new MockCreateProductUseCase();
ProductController controller = new ProductController(mockUseCase);
String requestBody = "{\"name\":\"Laptop\", \"price\":1200.00}";
String response = controller.createProductEndpoint(requestBody);
System.out.println("Controller Response: " + response);
if (mockUseCase.wasCalled()) {
System.out.println("Test PASSED: Use Case was invoked.");
} else {
System.out.println("Test FAILED: Use Case not invoked.");
}
}
}End-to-End (E2E) Tests
End-to-End tests simulate a complete user journey through the entire system, from the UI (or API client) to the database and back. They cover all layers and external services.
While slow and expensive, E2E tests provide the highest confidence that the whole system works together as intended. They are crucial for critical business flows.
Benefits of Layered Testing
Implementing a layered testing strategy in Clean Architecture brings significant benefits:
- Faster Feedback: Unit tests give immediate results.
- Easier Debugging: Failures are isolated to specific layers.
- Robust Architecture: Ensures each component and interaction works.
- Confidence in Changes: Allows safe refactoring and new feature development.
- CI/CD Ready: Supports automated pipelines effectively.
Check Your Knowledge
Let's check your understanding of layered testing in Clean Architecture.
Recap: Testing Clean Systems
You've learned how to develop a comprehensive layered testing strategy for Clean Architecture. We covered:
- The Test Pyramid and its levels: Unit, Integration, and E2E.
- Unit testing Entities and Use Cases, often using mocks.
- Integration testing adapters like Repositories and Controllers.
- The role of End-to-End tests for full system validation.
By applying these strategies, you ensure your Clean Architecture codebase is robust, maintainable, and reliable.
자주 묻는 질문
“계층별 테스트 전략” 강의는 무료인가요?
네 — “계층별 테스트 전략” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Clean Architecture & Design Patterns in Practice 강의 전체를 잠금 해제할 수 있습니다. Clean Architecture & Design Patterns in Practice 강의에는 총 4개의 강의가 포함되어 있습니다.
“계층별 테스트 전략”에서 뭘 배우나요?
클린 아키텍처의 모든 계층에서 단위, 통합, 엔드투엔드 테스트를 아우르는 종합적인 테스트 전략을 개발합니다. 브라우저에서 직접 실행하는 실습 코드로 Clean Architecture & Design Patterns in Practice을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Clean Architecture & Design Patterns in Practice을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Clean Architecture & Design Patterns in Practice은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.
“계층별 테스트 전략” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Clean Architecture & Design Patterns in Practice 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Clean Architecture & Design Patterns in Practice 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.