integration-testing

To test rollback and timeout paths across real infrastructure seams, use Testcontainers for deterministic databases and assert persistent state alongside emitted side effects beyond standard HTTP success responses.

Mock-only tests hide constraint, rollback, and serialization failures. Validating connected components across real infrastructure boundaries using Testcontainers ensures actual database queries and serialization behave correctly.

Set up deterministic integration testing by controlling external HTTP adapters with WireMock or nock, and using Testcontainers for queues like Kafka to isolate test data and verify seam behavior.

Yes, you can use Testcontainers and WireMock for controller-service-repository flow testing. This approach exercises real database queries, serialization, and auth context under controlled, isolated environments.

The best way to verify failure-path correctness is asserting both persisted state and side effects including rollback, timeouts, and partial-write behavior using deterministic infrastructure via Testcontainers.