zod-contract-testing

You can test Zod schemas for boundary validation by applying testValidInput and testInvalidInput utilities to ensure your API handlers correctly accept valid data and reject invalid payloads at system boundaries.

Schema evolution testing verifies that your Zod schemas remain stable and evolvable across versions. You use testSchemaEvolution and generateVersionCompatibilityMatrix to enforce version compatibility rules for runtime data contracts.

Yes, you can test Zod refinements using testRefinement and generate compound state matrices for 2^N optional fields with generateCompoundStateMatrix to verify complex boundary validation logic.

Zod contract testing applies to WebSocket messages and data migrations by validating runtime data contracts at these system boundaries, ensuring stable interfaces and preventing schema drift from affecting downstream logic.

The best way to prevent schema drift is to enforce boundary-tested Zod schemas at system boundaries, catching invalid data early and ensuring stable, evolvable interfaces across multiple versions using compatibility matrices.

You need to generate a version compatibility matrix when evolving your Zod schemas across versions, using generateVersionCompatibilityMatrix to verify that interface changes maintain stable contracts for runtime data ingestion.