unit-test

To write Vitest tests for Zod schemas with 100% coverage, create test files in __tests__/ directories mirroring the source structure, use safeParse() for validation, and cover valid inputs, invalid inputs, optional fields, and edge cases.

The standard naming convention for Zod schema test files is {type}.schema.spec.ts, placed inside a __tests__/ directory that mirrors the source file structure to maintain organization and clarity.

You should use safeParse() instead of parse() when testing Zod schemas. safeParse() returns a structured success object without throwing exceptions, allowing you to explicitly assert invalid inputs and edge cases gracefully.

To enforce strict Zod object schemas in Vitest tests, include test scenarios that pass unknown properties and assert the schema rejects them. This ensures unexpected fields are not silently ignored during validation.

Yes, you can use Vitest to test all Zod schema types including Assets, Receipts, Audit, and Reference. The testing scope covers all these schema types to ensure comprehensive validation across the schemas package.

When testing Zod schema validations, cover edge cases including invalid inputs, missing optional fields, and unknown properties. Additionally, test enumerations across all types to ensure strict schema enforcement and robust validation.