Integration Test

Overview

An integration test verifies that two or more components work correctly when wired together through a real boundary — a database, queue, HTTP client, or file system. The use of real infrastructure is intentional; that is what distinguishes it from a unit test.

Required background: Apply auto-test universal principles first. This skill adds integration-scope specifics.

When to Use

• Testing that a repository layer reads/writes to a real database correctly
• Testing that an event producer puts the expected message on a queue
• Testing that two modules integrate via their real interface
• Diagnosing failures that only appear against real infrastructure

Not for: logic-only behaviour where a double would suffice (use unit-test). Not for full user flows (use e2e-test).

Core Principles