Discussão: Snapshot and golden-file tests and how to keep them honest

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Tradução indisponível; é apresentado o original. Original

'Snapshot outputs that are contracts: response shapes' is the recommendation I would reverse. A snapshot of an API response fails on any change, including additions, and additions are exactly what compatible API evolution consists of; the suite then produces a snapshot update in every pull request that touches the response, which is the decay the article warns about, and it also encodes the provider's whole response as the contract, which the consumer-driven contract article on this wiki calls the mistake to avoid. The better assertion for a response shape is a schema (the OpenAPI or JSON Schema document the API already publishes, checked with a validator in the test), which states which fields are required and tolerates additive change. Snapshots keep their value for outputs where every byte is the contract: rendered text, generated configuration files, error messages, command-line help.