Code quality
Test Snapshot Cleanup: Delete Obsolete Golden Files With Confidence
Test snapshot cleanup begins when golden files, serialized fixtures, screenshots, and expected outputs no longer describe supported product behavior.
The useful output is a snapshot cleanup pull request with behavior map, deleted files, replacement assertions, review screenshots or output, and rollback note. Keep the review concrete: Replace broad snapshots with focused assertions before deleting coverage, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when approving output drift that still represents a real regression.
Key takeaways
- Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
- Use several CI cycles plus one release window for the protected behavior before deciding that “quiet” means “unused.”
- Prefer reversible changes first when approving output drift that still represents a real regression is still plausible.
- Leave behind a snapshot cleanup pull request with behavior map, deleted files, replacement assertions, review screenshots or output, and rollback note so the next review starts with context.
- Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.
Map Protected Behavior
Start with one test suite or component area across snapshots, fixture data, product states, visual diffs, reviewers, and release behavior. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.
| Field | Why it matters |
|---|---|
| Owner | Cleanup needs a person or team that can accept the decision |
| Current purpose | A short reason to keep the item, written in present tense |
| Last meaningful use | owners, callers, last change, runtime behavior, and deletion confidence |
| Dependency evidence | repository search, tests, logs, deploy history, and owner review |
| Risk if wrong | The outage, data loss, access failure, or rollback gap the review must avoid |
| Next action | Keep, reduce, archive, disable, remove, or investigate |
Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.
Snapshot Evidence to Review
The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For test snapshot cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Covered behavior | Component, API response, CLI output, visual state, and product requirement | The snapshot protects behavior that no longer ships |
| Change history | Snapshot updates, review comments, flaky diffs, and product decision notes | The file has become approval noise |
| Failure value | Bugs caught, regressions missed, and assertions duplicated elsewhere | The snapshot no longer catches unique risk |
| Replacement assertion | Focused test, visual baseline, schema check, or product-level integration test | Important behavior remains covered after deletion |
Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.
If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.
Example Evidence Check
Find snapshot files, update history, and related tests before deleting golden output.
rg "toMatchSnapshot|toMatchInlineSnapshot|golden|fixture|snapshot" tests src
rg "${SNAPSHOT_NAME}|${COMPONENT_NAME}" tests src docs
git log --oneline -- '**/__snapshots__/**' 'tests/fixtures/**'Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.
Replace Broad Assertions
Use the least permanent move that proves the decision. In test snapshot cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.
- Replace broad snapshots with focused assertions before deleting coverage.
- Review changed golden files with the product state visible.
- Delete obsolete fixtures and snapshots in the same pull request as the behavior they represented.
Track the cleanup candidate with a simple priority score:
| Score | Good sign | Bad sign |
|---|---|---|
| Impact | Meaningful spend, risk, toil, noise, or confusion disappears | The item is cheap and low-risk but politically distracting |
| Confidence | Owner, purpose, and dependency path are understood | The team is guessing from age or name |
| Reversibility | Restore, recreate, re-enable, or rollback path exists | Deletion would be the first real test |
| Prevention | A rule can stop recurrence | The same pattern will return next month |
Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.
Golden Files That Still Matter
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- Accessibility output, generated API contracts, invoice PDFs, emails, and localized copy.
- Visual snapshots that protect layout regressions not covered elsewhere.
- Golden files used by downstream SDK or CLI users.
For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.
Run the Snapshot Cleanup
Run test snapshot cleanup as a decision review, not an open-ended hygiene project.
- Pick the narrow scope and export the candidate list.
- Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
- Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
- Apply the least permanent useful change first.
- Watch the signals that would reveal a bad decision.
- Complete the final removal only after the review window closes.
- Save a snapshot cleanup pull request with behavior map, deleted files, replacement assertions, review screenshots or output, and rollback note.
For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.
Keep Snapshots Intentional
Prevention should change the creation path, not just the cleanup path. For test snapshot cleanup, the useful prevention fields are owner, reason to exist, removal trigger, and verification notes. Make those fields part of normal creation and review.
- Create snapshots with a named behavior and owner, not as default test output.
- Require snapshot updates to explain the product change they approve.
- Review stale snapshots when features, templates, or schemas are retired.
The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.
Example Decision Record
Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.
| Field | Example entry for this cleanup |
|---|---|
| Candidate | Obsolete test snapshots in software test suites |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Covered behavior, Change history, and owner confirmation |
| First reversible move | Replace broad snapshots with focused assertions before deleting coverage |
| Watch signal | The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong |
| Final action | Keep, reduce, archive, disable, or remove after several CI cycles plus one release window for the protected behavior |
| Prevention rule | Create snapshots with a named behavior and owner, not as default test output |
This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.
FAQ
How often should teams do test snapshot cleanup?
Use several CI cycles plus one release window for the protected behavior for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.
What is the safest first action?
The safest first action is usually ownership repair plus evidence collection. After that, replace broad snapshots with focused assertions before deleting coverage. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to accessibility output, generated api contracts, invoice pdfs, emails, and localized copy. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.
How do you make the decision useful later?
Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.