snapshot-testing

Facilitate snapshot testing in .NET applications using the Verify framework.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill snapshot-testing-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snapshot-testing
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/snapshot-testing
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill snapshot-testing-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of snapshot testing in .NET applications, ensuring that outputs like API responses, rendered components, and serialized data do not change unintentionally.

Core Features & Use Cases

  • Automated Baseline Verification: Captures and compares output against human-approved baselines, failing on unexpected changes.
  • Scrubbing Non-Deterministic Values: Automatically handles dynamic data like dates, GUIDs, and timestamps to ensure stable test results.
  • Use Case: When refactoring a complex API, use this Skill to snapshot test all response payloads. Any unintended changes to the API contract will be immediately flagged, preventing regressions.

Quick Start

Use the snapshot-testing skill to verify the output of the GetOrders_ResponseMatchesSnapshot test.

Frequently Asked Questions about snapshot-testing

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

FAQPage Schema
How do I automate .NET snapshot testing for API responses?

Scrubbing non-deterministic values in snapshot tests automatically handles dynamic data like dates, GUIDs, and timestamps to ensure stable test results. This technique prevents false test failures caused by changing temporal or unique identifier data.

Can I use snapshot testing to verify HTML rendering in .NET?

Using snapshot testing to verify HTML rendering in .NET captures the rendered component output and compares it against an approved baseline file. This approach detects unintended visual or structural markup changes automatically.

What is the best way to detect public API surface changes in .NET?

Detecting public API surface changes in .NET is best achieved through snapshot testing using Verify to approve the public contract. Any unintended modifications to the API surface are immediately flagged as test failures.

How do I handle non-deterministic data like GUIDs and dates in snapshot tests?

Handling non-deterministic data like GUIDs and dates in snapshot tests requires scrubbing dynamic values automatically. This ensures stable test results by normalizing unpredictable temporal and unique identifier outputs before comparison.