qa-snapshot-tests

Lock serialized outputs as committed artifacts requiring human review for updates.

6|Updated Apr 24, 2026

Search Tags:#testing #qa #governance #review #serialization #snapshot #update-policy

Ready to run

npx skills add https://github.com/lookatitude/guild --skill qa-snapshot-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-snapshot-tests
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/qa-snapshot-tests
Command: npx skills add https://github.com/lookatitude/guild --skill qa-snapshot-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locks a serialized or rendered output as a committed artifact and enforces human review on every update to prevent unmanaged drift and flaky results.

Core Features & Use Cases

Snapshot tests: one test per serialized unit, with normalized outputs.
Custom serializers: shared module to scrub nondeterminism and redact noise.
Update policy: a concise policy doc detailing who may approve changes and when to update.
Review checklist: a two-line checklist referenced in PR templates.
Rot guard: optional test or lint to flag snapshots that have not changed in N months.

Quick Start

Run a snapshot-test workflow to generate and review the snapshot suite for your project.

Frequently Asked Questions about qa-snapshot-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce review on snapshot test updates to prevent unmanaged drift?▼

You can enforce review on snapshot test updates by locking serialized outputs as committed artifacts and applying an explicit update policy. This governs changes by requiring human approval on every diff to prevent flaky results.

What is the best way to manage nondeterminism in serialized outputs for snapshot testing?▼

The best way to manage nondeterminism in serialized outputs is by using custom serializers. These shared modules scrub nondeterministic data and redact noise to normalize outputs before locking them as committed artifacts.

How do I set up a governance policy for UI component snapshot testing?▼

To set up a governance policy for UI component snapshot testing, create a concise policy doc detailing who may approve changes and when to update. You should also reference a review checklist directly in your PR templates.

How can I detect stale snapshots that have not changed in several months?▼

You can detect stale snapshots by implementing rot guard, which is an optional test or lint rule. It flags snapshots that have not changed in N months to prevent unmanaged drift in your serialized test outputs.

Does this snapshot testing approach work for generated data graphs?▼

Yes, this snapshot testing approach works for generated data graphs. It locks serialized outputs as committed artifacts and enforces one test per serialized unit, ensuring changes to generated data graphs require explicit review.