Integration Testing

Integration tests validate real boundaries: HTTP APIs, databases, queues, platform SDK adapters, and service interactions. They run after deployment in Dev or Test when live dependencies are required.

Tests are tagged by required environment and data set. They create isolated data, clean up after themselves, and avoid destructive operations against shared resources. API tests use stable public contracts and include authentication, authorization, validation, retry, and error scenarios.

Integration failures block release readiness even when application CI has passed. Results are published centrally with links from the release evidence.