Snapshots vs Explicit Assertions
You'll learn: When to choose explicit assertions over snapshots for more maintainable, intentional tests.
The Core Trade-off
Snapshots are convenient—they capture entire outputs automatically. But this convenience comes at a cost: they make it easy to approve changes without truly understanding them. Explicit assertions, on the other hand, require you to state exactly what matters in your test, making your intent crystal clear.
Think of snapshots like taking a photo of your entire room to verify it's clean. An explicit assertion is like checking "Is the bed made? Are dishes washed?"—you're testing specific, meaningful conditions.
When to Prefer Explicit Assertions
Use explicit assertions when:
- The critical behavior is specific: Testing that a function returns
status: 200is clearer than snapshotting the entire response object - You want failures to be obvious:
expect(user.age).toBe(18)immediately shows what broke; a snapshot diff might bury the same change in noise - The output has incidental details: Timestamps, random IDs, or formatting details pollute snapshots but can be ignored with targeted assertions
- Your test intent matters more than implementation: Assertions document why you care about certain values
When Snapshots Still Win
Snapshots remain useful for:
- Complex nested structures where every field matters (like configuration objects)
- UI component rendering where visual structure is the point
- Generated code or large outputs that are validated holistically
The key is intentionality. If you can't explain what would make the snapshot fail incorrectly, you probably need explicit assertions instead.
Key Takeaway: Prefer explicit assertions when you care about specific values or behaviors—they make test intent obvious and failures diagnostic. Reserve snapshots for when the entire structure matters and changes should be rare.