SnapshotAssertions 0.7.1
Prefix Reserveddotnet add package SnapshotAssertions --version 0.7.1
NuGet\Install-Package SnapshotAssertions -Version 0.7.1
<PackageReference Include="SnapshotAssertions" Version="0.7.1" />
<PackageVersion Include="SnapshotAssertions" Version="0.7.1" />
<PackageReference Include="SnapshotAssertions" />
paket add SnapshotAssertions --version 0.7.1
#r "nuget: SnapshotAssertions, 0.7.1"
#:package SnapshotAssertions@0.7.1
#addin nuget:?package=SnapshotAssertions&version=0.7.1
#tool nuget:?package=SnapshotAssertions&version=0.7.1
SnapshotAssertions
Scope: Test projects only. Not intended for production code.
Framework-agnostic core for text-snapshot assertions.
For TUnit test projects, install
SnapshotAssertions.TUnitinstead; this package comes with it transitively.SnapshotAssertionsis the framework-agnostic shared engine; framework-specific adapter packages add the assertion entry points each test framework expects.
What's in this package
SnapshotComparer: string-against-file comparison with line-ending, BOM, trailing-whitespace, and trailing-newline options.SnapshotFileResolver: TestContext-aware default file naming (Snapshots/{TestClass}.{TestMethod}.expected.txt) and explicit-path resolution.SnapshotAcceptMode: env-var-driven accept logic (SNAPSHOT_ACCEPT=1writes the actual content over the expected baseline) with aCI=trueguard so accidental pipeline acceptance is impossible.SnapshotOptions: line-ending, BOM, whitespace, and trailing-newline configuration with strict defaults, plus a caller-suppliedWithNormalizer(Func<string, string>)pre-comparison transform (v0.5.0+).LineDiffRenderer: terminal line-based diff display, truncated to the first 20 differing lines for very large diffs (LineDiffRenderer.MaxDifferingLines = 20).SnapshotScrubber+Scrubbersfactory (v0.2.0+): text-transform pipeline that replaces volatile substrings (GUIDs, ISO 8601 timestamps, Unix-epoch-millis numbers, custom regex matches) with stable indexed tokens before comparison. Built-ins (Scrubbers.Guid,Scrubbers.Iso8601Timestamp,Scrubbers.UnixEpochMillis, plusScrubbers.GuidNandScrubbers.ElapsedMs(v0.4.0+)), curated chains (Scrubbers.Defaultfor the v0.2.0 three-pattern set,Scrubbers.Common(v0.4.0+) for the extended five-pattern set), twoScrubbers.Patternoverloads for custom regex (flat literal token) plus twoScrubbers.IndexedPatternoverloads (v0.5.0+) for the indexed<kind:N>counterpart that keeps recurring matched values correlated, andSnapshotScrubberStatefor stable indexed-token assignment across recurring values.Scrubbers.Combine(params SnapshotScrubber[])(v0.3.0+) assembles an array of scrubbers into a single composite for reusable bundles.DiffSuggestion+DiffSuggestionAnalyzer(v0.4.0+): scans a snapshot-mismatch diff for known volatile patterns and surfaces scrubber recommendations. Integrated intoSnapshotResult.Describe()so failure messages include a top-3-capped "Suggestion(s)" section pointing at applicable built-ins.SnapshotAssertions.Render.SnapshotRenderer<T>+Renderer.For<T>(v0.4.0+): abstract base class and inline factory for projecting domain types to canonical strings before snapshot comparison. Adapter packages consume these via their ownMatchesSnapshot<T>overloads.
Test-framework adapters
| Package | Test framework | Status |
|---|---|---|
SnapshotAssertions.TUnit |
TUnit | Available now |
SnapshotAssertions.NUnit |
NUnit | Possible if there is demand |
SnapshotAssertions.xUnit |
xUnit | Possible if there is demand |
SnapshotAssertions.MSTest |
MSTest | Possible if there is demand |
If you'd find a non-TUnit adapter useful, open a feature request: adapters are not built proactively.
Installation
dotnet add package SnapshotAssertions.TUnit
SnapshotAssertions comes transitively. You don't need to install it directly unless you're building your own adapter package.
Stability
The public surfaces above are semver-bound. Breaking changes require a major version bump. The exact text format of line-based diff output is not stable and may gain extra detail or change formatting in any release.
License
MIT. Copyright (c) 2026 John Verheij.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on SnapshotAssertions:
| Package | Downloads |
|---|---|
|
SnapshotAssertions.TUnit
TUnit-native text-snapshot assertions using [AssertionExtension]. Provides Assert.That(actual).MatchesSnapshot() / .MatchesSnapshotFile() with line-based diff display, accept-via-environment-variable workflow, and CI guard. AOT-compatible, trimmable, no reflection. Designed for API-surface verification and small text snapshots; coexists with Verify for object-graph cases. |
GitHub repositories
This package is not used by any popular GitHub repositories.
View the rendered release notes: https://github.com/JohnVerheij/SnapshotAssertions.TUnit/releases/tag/v0.7.1
Patch release. Restores `build/SnapshotAssertions.TUnit.targets` to the package. 0.7.0 shipped without it, so a consumer's committed `Snapshots/*.expected.txt` baselines stopped copying to the test output directory and every snapshot assertion failed with "baseline does not exist". No public API change.
### Fixed
- **The package again ships `build/SnapshotAssertions.TUnit.targets`.** DotNetProjectFile.Analyzers 1.15.0 added `**/*.targets` to a SonarQube content glob marked `Pack="false"`, which silently overrode this package's explicit `Pack="true"` for its own build targets and dropped the file from the 0.7.0 `.nupkg`. That targets file auto-includes a consumer's `Snapshots/**/*.expected.txt` with `CopyToOutputDirectory="PreserveNewest"`, so without it the committed baselines never reach the test binary's output directory and the resolver reports them missing. Setting `SonarQubeIntegration=false` (the integration is unused in this package) restores the packed asset, and a CI check now asserts the produced `.nupkg` contains the build targets so it cannot silently drop again.
### Upgrade note
Consumers who applied the 0.7.0 workaround (a manual `<None Update="Snapshots/**/*.expected.txt" CopyToOutputDirectory="PreserveNewest" />` together with `<SnapshotAssertionsAutoIncludeSnapshots>false</SnapshotAssertionsAutoIncludeSnapshots>`) can remove both after upgrading; the package's own targets resume handling the copy. Leaving the workaround in place stays harmless.