testing

Structure tests by architectural layer: pure unit tests for Domain logic, mocked unit tests for Application logic, integration tests for Infrastructure repositories, and component integration tests for the Presentation layer. This ensures test suites remain maintainable and correctly scoped per layer.

Yes, when testing the application layer, you should mock Infrastructure Repositories and Zustand Stores. This isolates complex hook logic, query options, and state mutations, ensuring your tests validate application behavior without triggering actual infrastructure or network calls.

The best way to test domain layer business logic is using pure unit tests with zero mocks. Validate business logic and input schemas directly, such as calling `.parse()`, to ensure core utilities function correctly without any external dependencies or side effects.

Never mock axios, fetch, or useQuery directly inside presentation layer component tests. Instead, mock the Application Layer Hooks to test UI rendering across data states, user interactions, and accessibility while maintaining proper Clean Architecture boundaries.

Infrastructure layer tests use integration tests with mocked HTTP to verify that repositories correctly call endpoints, map DTOs to domain entities, and validate API shapes. Pure unit tests cannot adequately verify these external integrations and data mapping behaviors.