What is a common drawback of snapshot testing?

What is a common drawback of snapshot testing?

• A. It can be brittle with frequent UI changes.
• B. It provides total coverage of business logic.
• C. It does not support regression testing.
• D. It is always maintenance-free.

Answer: (A)

Snapshot testing compares the rendered output of a component to a stored snapshot to ensure the UI stays the same over time. The common drawback is brittleness when the UI changes frequently. Since the test checks the exact rendered structure, any legitimate change—like adding or removing elements, tweaking markup, or even small styling adjustments—will cause a snapshot mismatch. That means you end up updating snapshots often, which can become maintenance churn and may hide real issues if updates are made without careful review. Keep in mind these tests focus on the UI rendering, not the underlying business logic or behavior. They’re not a substitute for more targeted tests that exercise functionality and user interactions. Also, they’re not maintenance-free: as the UI evolves, snapshots require regular upkeep to stay meaningful. A practical approach is to keep snapshots small and stable, and complement them with tests that validate critical interactions and logic.

Snapshot testing compares the rendered output of a component to a stored snapshot to ensure the UI stays the same over time. The common drawback is brittleness when the UI changes frequently. Since the test checks the exact rendered structure, any legitimate change—like adding or removing elements, tweaking markup, or even small styling adjustments—will cause a snapshot mismatch. That means you end up updating snapshots often, which can become maintenance churn and may hide real issues if updates are made without careful review.

Keep in mind these tests focus on the UI rendering, not the underlying business logic or behavior. They’re not a substitute for more targeted tests that exercise functionality and user interactions. Also, they’re not maintenance-free: as the UI evolves, snapshots require regular upkeep to stay meaningful. A practical approach is to keep snapshots small and stable, and complement them with tests that validate critical interactions and logic.