Testing Integration

Overview

Use this skill to verify boundary behavior where independently correct units may still fail in combination.

Scope Boundaries

• Use when correctness depends on integration seams.
• Typical requests:
  • Validate repository-to-database behavior including failure paths.
  • Test timeout and retry handling between services.
  • Verify adapter replacement does not break boundary contracts.
• Do not use when:
  • The goal is full browser journey validation (testing-e2e/playwright).
  • The goal is pure isolated unit checks (testing-unit).

Inputs

• Integration seams and dependency topology
• Failure-mode expectations (timeout, retry, partial failure)
• Fixture/environment constraints