Home/Answers/Contract tests
JSON→TS / Contract tests

Contract tests FAQ

The most common Contract tests questions are format, quality, permissions, batch failures and privacy.

Updated 2026-10-31About 3 minLocal test
Quick answer

The most common Contract tests questions are format, quality, permissions, batch failures and privacy. Contract tests catch API changes before runtime breakage.

Why it matters

Checking these high-frequency issues solves most cases.

Cover success/error/empty responses.

Step by step

  1. Start with real/complete JSON covering optional fields and empty arrays.
  2. Check array elements, null/optional and nested objects.
  3. Set the root name and copy into the project.
  4. Add Zod/Valibot runtime validation for production.
  5. Add contract tests/versioning for API changes.

Common mistakes

  • Treating a sample as a complete schema, missing optional/empty arrays.
  • Trusting generated any/null unions as-is.
  • Forgetting quotes for property names with spaces/Chinese.
  • Skipping runtime validation after generation.

Checklist

  • Sample covers optional/empty arrays/null.
  • Array object fields merged.
  • Property/root names valid.
  • Runtime validation added.
  • API contract/version considered.

Key facts

  • Cover success/error/empty responses.
  • Version responses.

FAQ

What are common Contract tests questions?

The most common Contract tests questions are format, quality, permissions, batch failures and privacy. Contract tests catch API changes before runtime breakage.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: Pact