Testing Contract

Overview

Use this skill to prevent integration regressions by enforcing provider-consumer contracts in CI.

Scope Boundaries

• Use when interface compatibility between producer and consumer is a release risk.
• Typical requests:
  • Verify an API response change does not break existing consumers.
  • Enforce event schema compatibility in CI.
  • Add provider-consumer contract gates before merge.
• Do not use when:
  • The scope is visual/UI behavior only (testing-e2e or playwright).
  • The scope is isolated unit logic (testing-unit).

Inputs

• Contract definitions and compatibility policy
• Provider/consumer versioning constraints
• Release and rollback requirements