Property-based testing

How it works

Rather than hand-writing examples, you declare properties ('output is valid JSON matching the schema', 'the sum equals the total', 'no field is null') and let a generator hammer the system. It scales coverage far beyond manual cases and shrinks failures to minimal reproductions.

When to use it

Structured output, tool/function calling, anything with checkable invariants.

Limitations

Only as good as the properties you state; semantic correctness often can't be captured as a simple invariant.

Cite this