올클 테스트 작성 가이드 (v3 - 데이터 기반)

Backend testing requests are classified by distinguishing simple utility tests, Spring Boot integration tests, domain-format checks, and cases requiring human judgment. This classification prevents unsafe assumptions and ensures correct test type selection before writing code.

Avoid mocks for integration tests when verifying external-response or policy-driven behavior, as these represent red-line restrictions. Inspect call sites first or escalate the decision instead of writing brittle mock-based tests that violate repository-specific conventions.

AssertJ works with MockitoBean to enforce project-specific testing conventions, including async verification patterns. This combination ensures safe, data-grounded test authoring while maintaining repository-specific fixture usage and prohibited annotation restrictions.

The best way to test fetchers and schedulers is to classify the test request using documented rules, inspect call sites, and apply repository-specific conventions. Only write test types that risk levels allow, stopping to escalate when human judgment is required.

Safe integration tests for domain-format checks require applying repository-specific conventions for AssertJ and fixtures. Classify the scenario first, then write only the allowed test type while enforcing async verification patterns and red-line restrictions.

Backend test classification fails on external API responses because policy-driven behavior represents a red-line restriction. The testing guardrails require you to stop and escalate these cases rather than making unsafe assumptions about external-response behavior.