testing-strategy

A test strategy for hexagonal architecture maps tests to specific layers: unit tests for the Domain, integration tests for Application and Infrastructure adapters, and end-to-end tests for HTTP controllers and Full-stack flows. This separation ensures coverage targets the correct boundary without overlapping scopes.

Distributing tests in a test pyramid requires selecting a ratio across unit, integration, and e2e layers. The strategy specifies what to test and where it should run, balancing fast feedback from unit tests with the confidence of end-to-end tests while minimizing flaky-test remediation overhead.

Contract testing using Pact validates interactions across hexagonal service boundaries by defining consumer-driven contracts. This strategy specifies Pact as the tooling to verify integration points, ensuring services communicate correctly without requiring full end-to-end deployments for every validation.

Vitest and Playwright can be selected together to cover full-stack test coverage. Vitest handles unit and component tests for frontend and domain layers, while Playwright executes end-to-end tests across HTTP controllers and full-stack user flows.

A testing strategy during project initialization prevents inconsistent coverage and flaky tests. It establishes clear validation guardrails, selects appropriate tooling like Testing Library and Pact, and defines data strategies before code is written, ensuring scalable test architecture.