Verify

Verify

Verify is a snapshot tool that simplifies the assertion of complex data models and documents.

Verify is called on the test result during the assertion phase. It serializes that result and stores it in a file that matches the test name. On the next test execution, the result is again serialized and compared to the existing file. The test will fail if the two snapshots do not match: either the change is unexpected, or the reference snapshot needs to be updated to the new result.

See Milestones for release notes.

Open Source Maintenance Fee

This project participates in the Open Source Maintenance Fee. The source code stays freely available under the terms of the license. The fee covers the use of the official binary releases, the packages published to NuGet, by organizations that generate revenue from them. Every version released after 1 September 2026 is covered; versions released on or before that date are not.

The fee is paid by sponsoring VerifyTests at the monthly tier matching the size of the organization:

From v33, sponsorship is verified at build time by SponsorCheck. Nothing phones home: the check runs inside the build, adds no runtime dependency to the packages, and issues no license keys. A sponsoring organization declares its account once, in a Directory.Build.props at the root of the repository, and that covers every project and every Verify package:

<PropertyGroup>
  <Verify_GitHubSponsorAccount>your-github-account</Verify_GitHubSponsorAccount>
</PropertyGroup>

Each Verify version bundles the sponsor list as it stood when that version was packed, so a sponsorship that began later also needs <Verify_SponsorshipStart>yyyy-MM-dd</Verify_SponsorshipStart> until the next upgrade. A sponsorship made private on GitHub is never bundled, so it also needs <Verify_SponsorshipPrivateUntil>yyyy-MM</Verify_SponsorshipPrivateUntil>, set at most 12 months out and renewed when it lapses.

Who the fee applies to, paying by invoice, and the other declarations (exemptions, private arrangements, opting out) are covered in Open Source Maintenance Fee. The SponsorCheck setup wizard for Verify generates the exact snippet for any of them.

Supporters

Entity Framework Extensions

Entity Framework Extensions is a major sponsor and is proud to contribute to the development this project.

Developed using JetBrains IDEs

Duende Software

Authentication and authorization via

TestMu AI

Browser testing via

Requirements

• Supported runtimes: net462, net472, net48, net481, net6, net8, net9, and net10.
• Supported SDK: 9.0.301 and up

Getting started wizard

Get customized instructions for the specific combination of Operating System, IDE, Test Framework, and Build Server.

Start wizard.

NuGet

• https://nuget.org/packages/Verify.NUnit/
• https://nuget.org/packages/Verify.XunitV3/
• https://nuget.org/packages/Verify.Fixie/
• https://nuget.org/packages/Verify.Expecto/
• https://nuget.org/packages/Verify.MSTest/
• https://nuget.org/packages/Verify.TUnit/

Snapshot management

Accepting or declining a snapshot file is part of the core workflow of Verify. There are several ways to do this and the approach(s) selected is a personal preference.

• In the Windows Tray via DiffEngineTray
• ReSharper test runner plugin (Source)
• Rider test runner plugin (Source)
• Via the clipboard.
• Manually making the change in the launched diff tool. Either with a copy paste, or some tools have commands to automate this via a shortcut or a button.
• Manually on the file system, by renaming the .received. file to .verified.. This can be automated via scripts to bulk accept all .received. files by matching a pattern.
• Using the dotnet tool Verify.Terminal.

Usage

ImplicitUsings

All examples use Implicit Usings. Ensure <ImplicitUsings> is set to enable to ensure examples compile correctly.

<ImplicitUsings>enable</ImplicitUsings>

If ImplicitUsings are not enabled, substitute usages of Verify() with Verifier.Verify().

Class being tested

Given a class to be tested:

public static class ClassBeingTested
{
    public static Person FindPerson() =>
        new()
        {
            Id = new("ebced679-45d3-4653-8791-3d969c4a986c"),
            Title = Title.Mr,
            GivenNames = "John",
            FamilyName = "Smith",
            Spouse = "Jill",
            Children =
            [
                "Sam",
                "Mary"
            ],
            Address = new()
            {
                Street = "4 Puddle Lane",
                Country = "USA"
            }
        };
}

^{snippet source | anchor}

NUnit

Support for NUnit

[TestFixture]
public class Sample
{
    [Test]
    public Task Test()
    {
        var person = ClassBeingTested.FindPerson();
        return Verify(person);
    }
}

^{snippet source | anchor}

xUnitV3

Support for xUnitV3

public class Sample
{
    [Fact]
    public Task Test()
    {
        var person = ClassBeingTested.FindPerson();
        return Verify(person);
    }
}

^{snippet source | anchor}

Fixie

Support for Fixie

public class Sample
{
    public Task Test()
    {
        var person = ClassBeingTested.FindPerson();
        return Verify(person);
    }
}

^{snippet source | anchor}

Fixie is less opinionated than other test frameworks. As such it leaves up to the consumer how to configure test execution.

To enable Verify the ITestProject and IExecution interfaces need to be used.

Requirements:

• Assign the target assembly in ITestProject.Configure using VerifierSettings.AssignTargetAssembly
• Wrap test executions in IExecution.Run using ExecutionState.Set

An example implementation of the above:

public class TestProject :
    ITestProject,
    IExecution
{
    public void Configure(TestConfiguration configuration, TestEnvironment environment)
    {
        VerifierSettings.AssignTargetAssembly(environment.Assembly);
        configuration.Conventions.Add<DefaultDiscovery, TestProject>();
    }

    public async Task Run(TestSuite testSuite)
    {
        foreach (var testClass in testSuite.TestClasses)
        {
            foreach (var test in testClass.Tests)
            {
                if (test.HasParameters)
                {
                    foreach (var parameters in test
                                 .GetAll<TestCase>()
                                 .Select(_ => _.Parameters))
                    {
                        using (ExecutionState.Set(testClass, test, parameters))
                        {
                            await test.Run(parameters);
                        }
                    }
                }
                else
                {
                    using (ExecutionState.Set(testClass, test, null))
                    {
                        await test.Run();
                    }
                }
            }
        }
    }
}

^{snippet source | anchor}

Expecto

Support for Expecto

open Expecto
open VerifyTests
open VerifyExpecto

[<Tests>]
let tests =
    testTask "findPerson" {
        let person = ClassBeingTested.FindPerson()
        do! Verifier.Verify("findPerson", person).ToTask()
    }

^{snippet source | anchor}

Caveats

Due to the nature of the Expecto implementation, the following APIs in Verify are not supported.

• settings.UseParameters()
• settings.UseTextForParameters()

TUnit

Support for TUnit

public class Sample
{
    [Test]
    public Task Test()
    {
        var person = ClassBeingTested.FindPerson();
        return Verify(person);
    }
}

^{snippet source | anchor}

MSTest

Support for MSTest

[TestClass]
public partial class Sample
{
    [TestMethod]
    public Task Test()
    {
        var person = ClassBeingTested.FindPerson();
        return Verify(person);
    }
}

^{snippet source | anchor}

Marking tests as ‘Using Verify’

The MSTest implementation leverages a Source Generator and requires test classes to opt in to being processed by the Source Generator.

Add the UsesVerifyAttribute.

For all test classes in an assembly:

[assembly: UsesVerify]

For a specific a test class:

[UsesVerify]
[TestClass]
public class TheTest...

Or inherit from VerifyBase:

[TestClass]
public class VerifyBaseUsage :
    VerifyBase
{
    [TestMethod]
    public Task Simple() =>
        Verify("The content");
}

^{snippet source | anchor}

Initial Verification

No existing .verified. file.

When the test is initially run it will fail. If a Diff Tool is detected it will be used to display the diff.

To verify the result:

• Execute the command from the Clipboard, or
• Accept with DiffEngineTray tool,
• Accept with ReSharper Plugin or Rider Plugin
• Use the diff tool to accept the changes, or
• Manually copy the text to the new file

Verified result

This will result in the Sample.Test.verified.txt being created:

{
  GivenNames: John,
  FamilyName: Smith,
  Spouse: Jill,
  Address: {
    Street: 4 Puddle Lane,
    Country: USA
  },
  Children: [
    Sam,
    Mary
  ],
  Id: Guid_1
}

^{snippet source | anchor}

Subsequent Verification

Existing .verified. file.

If the implementation of ClassBeingTested changes:

public static class ClassBeingTested
{
    public static Person FindPerson() =>
        new()
        {
            Id = new("ebced679-45d3-4653-8791-3d969c4a986c"),
            Title = Title.Mr,
            // Middle name added
            GivenNames = "John James",
            FamilyName = "Smith",
            Spouse = "Jill",
            Children =
            [
                "Sam",
                "Mary"
            ],
            Address = new()
            {
                // Address changed
                Street = "64 Barnett Street",
                Country = "USA"
            }
        };
}

^{snippet source | anchor}

And the test is re-run it will fail.

The Diff Tool will display the diff:

The same approach can be used to verify the results and the change to Sample.Test.verified.txt is committed to source control along with the change to ClassBeingTested.

Async

Verify() has overloads that accept Task<T>, ValueTask<T>, and IAsyncEnumerable<T>. These are awaited before verification.

There is also an overload that accepts Func<Task<T>>, which works well with async lambda expressions:

await Verify(
    async () => new
    {
        Foo = await repo.GetFoo(id),
        Bars = await repo.GetBars(id)
    });

^{snippet source | anchor}

VerifyJson

VerifyJson performs the following actions

• Convert to JToken (if necessary).
• Apply ignore member by name for keys.
• PrettyPrint the resulting text.

[Fact]
public Task VerifyJsonString()
{
    var json = "{'key': {'msg': 'No action taken'}}";
    return VerifyJson(json);
}

[Fact]
public Task VerifyJsonStream()
{
    var json = "{'key': {'msg': 'No action taken'}}";
    var stream = new MemoryStream(Encoding.UTF8.GetBytes(json));
    return VerifyJson(stream);
}

[Fact]
public Task VerifyJsonJToken()
{
    var json = "{'key': {'msg': 'No action taken'}}";
    var target = JToken.Parse(json);
    return Verify(target);
}

^{snippet source | anchor}

Results in a .txt file:

{
  key: {
    msg: No action taken
  }
}

^{snippet source | anchor}

Conventions

Source control Includes/Excludes

• All *.received.* files should be excluded from source control.

eg. add the following to .gitignore

*.received.*

If using UseSplitModeForUniqueDirectory also include:

*.received/

All *.verified.* files should be committed to source control.

Text file settings

Text variants of verified and received have the following characteristics:

• UTF8 with a Byte order mark (BOM)
• Newlines as line-feed (lf)
• No trailing newline

This manifests in several ways:

Source control settings

All text extensions of *.verified.* should have:

• eol set to lf
• working-tree-encoding set to UTF-8

Note: working-tree-encoding=UTF-8 is correct even though Verify writes files with a BOM. Git does not strip or add the BOM - it passes through transparently. The UTF-8-BOM encoding would explicitly add a BOM on checkout and strip it on commit (so the internal blob differs from the working tree), but that is not the desired behavior since Verify writes the BOM itself and it should be preserved in the blob.

All Binary files should also be marked to avoid merging and line ending issues with binary files.

eg add the following to .gitattributes

*.verified.txt text eol=lf working-tree-encoding=UTF-8
*.verified.xml text eol=lf working-tree-encoding=UTF-8
*.verified.json text eol=lf working-tree-encoding=UTF-8
*.verified.bin binary

Line ending autocrlf

On Windows, if core.autocrlf is set to true, files may show as modified with no actual content changes. To fix this:

git config --global core.autocrlf input

core.autocrlf=true normalizes line endings to lf on commit, and converts them back to crlf on checkout. So the blobs stored in git are lf while the files on disk are crlf. Verify rejects a verified file containing a carriage return, so tests fail even though the committed content is correct.

Adding the .gitattributes entries above overrides core.autocrlf for those paths, but it does not update files that are already checked out. Git re-applies line ending filters only when a file’s blob changes, and since core.autocrlf already normalized those blobs to lf, adding the attributes changes no content. A one-time refresh of the working tree is required after committing .gitattributes:

git rm --cached -r .
git reset --hard

This discards uncommitted changes, so commit or stash first.

Where crlf was committed to the blobs (core.autocrlf unset or false), the content itself needs normalizing instead. In that case git add --renormalize . produces a commit that converts the blobs, and checkout updates each working tree as it is pulled:

git add --renormalize .
git commit -m "Normalize line endings"

Build servers that reuse a cached working directory between runs need the same refresh as a developer machine. A build that clones fresh each run is unaffected.

EditorConfig settings

If modifying text verified/received files in an editor, it is desirable for the editor to respect the above conventions. For EditorConfig enabled the following can be used:

# Verify settings
[*.{received,verified}.{json,txt,xml}]
charset = utf-8-bom
end_of_line = lf
indent_size = unset
indent_style = unset
insert_final_newline = false
tab_width = unset
trim_trailing_whitespace = false

[*.{received,verified}.{json,xml,html,htm,yaml,svg}]
indent_size = 2
indent_style = space

Note that the above are suggested for subset of text extension. Add others as required based on the text file types being verified.

Visual Studio Code does not apply the EditorConfig end_of_line setting natively. Without it, accepting a snapshot by editing in the built-in diff editor (for example reverting a block from received into verified) can save the verified file with crlf on Windows, taken from the default files.eol. Verify then rejects that file for containing a carriage return. Installing the EditorConfig for VS Code extension applies end_of_line = lf on save. Setting "files.eol": "\n" in Visual Studio Code settings has the same effect without the extension.

Newline tolerance

The settings above are the recommended approach, since they keep the content on disk consistent for everyone working on a repository. Where per developer setup cannot be relied on, Verify can instead be made tolerant of carriage returns and of a trailing newline in verified files. Both are opt in, and both have side effects worth understanding before enabling them. See Newline tolerance.

Conventions check

The above conventions can be checked by calling VerifyChecks.Run() in a test

MSTest

[TestClass]
public partial class VerifyChecksTests
{
    [TestMethod]
    public Task Run() =>
        VerifyChecks.Run();
}

^{snippet source | anchor}

Expecto

public class VerifyChecksTests
{
    [Tests]
    public static Test verifyChecksTest = Runner.TestCase(
        nameof(verifyChecksTest),
        () => VerifyChecks.Run(typeof(VerifyChecksTests).Assembly));
}

^{snippet source | anchor}

Fixie

public class VerifyChecksTests
{
    public Task Run() =>
        VerifyChecks.Run(GetType().Assembly);
}

^{snippet source | anchor}

XunitV3

public class VerifyChecksTests
{
    [Fact]
    public Task Run() =>
        VerifyChecks.Run();
}

^{snippet source | anchor}

TUnit

public class VerifyChecksTests
{
    [Test]
    public Task Run() =>
        VerifyChecks.Run();
}

^{snippet source | anchor}

Static settings

Most settings are available at both the global level and at the instance level.

When modifying settings at the global level it should be done using a Module Initializer:

public class StaticSettings
{
    [Fact]
    public Task Test() =>
        Verify("String to verify");
}

public static class StaticSettingsUsage
{
    [ModuleInitializer]
    public static void Initialize() =>
        VerifierSettings.AddScrubber(_ => _.Replace("String to verify", "new value"));
}

^{snippet source | anchor}

In .net framework, where the Module Initializer feature is not enabled by default, either use a Polyfill package (eg https://github.com/SimonCropp/Polyfill) or add the following to the test project:

namespace System.Runtime.CompilerServices;

[AttributeUsage(AttributeTargets.Method, AllowMultiple = false)]
public sealed class ModuleInitializerAttribute : Attribute;

Alternatively, place static settings in the “run once before all test” API of the test framework being used.

VerifyResult

In some scenarios it can be helpful to get access to the resulting *.verified.* files after a successful run. For example to do an explicit check for contains or not-contains in the resulting text. To allow this all Verify methods return a VerifyResult.

var result = await Verify(
    new
    {
        Property = "Value To Check"
    });
Assert.Contains("Value To Check", result.Text);

^{snippet source | anchor}

If using Verifier.Throws, the resulting Exception will also be accessible

var result = await Throws(MethodThatThrows);
Assert.NotNull(result.Exception);

^{snippet source | anchor}

CurrentFile

Utility for finding paths based on the current file.

using IOPath = System.IO.Path;

namespace VerifyTests;

public static class CurrentFile
{
    public static string Path([CallerFilePath] string file = "") =>
        file;

    public static string Directory([CallerFilePath] string file = "") =>
        IOPath.GetDirectoryName(file)!;

    public static string Relative(string relative, [CallerFilePath] string file = "")
    {
        var directory = IOPath.GetDirectoryName(file)!;
        return IOPath.Combine(directory, relative);
    }
}

^{snippet source | anchor}

Versioning

Verify follows Semantic Versioning. The same applies for extensions to Verify. Small changes in the resulting snapshot files may be deployed in a minor version. As such nuget updates to Verify.* should be done as follows:

• Update all Verify.*packages in isolation
• Re-run all tests.
• If there are changes, ensure they look correct given the release notes. If the changes do not look correct, raise an issue.
• Accept the changes.

Snapshot changes do not trigger a major version change to avoid causing Diamond dependency issues for downstream extensions.

Unit testing inside virtualized environment

Unit tests referencing Verify (including unit tests within this repository as well as any other code referencing Verify) can be run and debugged on a local virtualized environment supported by Visual Studio Remote Testing. Initial configurations have been added for WSL and net 7.0 linux docker via testenvironments.json (for third party code, the file needs to be copied or recreated next to the .sln solution file for solution to leverage the functionality).

Upon opening the Tests Explorer the advanced environments are available in the GUI:

This readme will not discuss definitive list of details for proper setup of the environments instead refer the following information sources and warn about particular gotchas:

• WSL runs
  • Install WSL.
  • Install a distribution.
  • Install .NET Runtime
• Docker runs
  • Install Docker Desktop
  • First run of docker scenario might need elevation (Test project does not reference any .NET NuGet adapter error)
• Third party test runners might not support this feature. Use Visual Studio Test Explorer.

Project inclusion for *.received.* and *.verified.* files

Verify comes with default MSBuild includes for snapshot files (*.received.* and *.verified.*) that nests those files under the test that produced them. C#, VB and F# projects are supported. In Blazor projects, snapshots nest under the .razor.cs code-behind of the component under test, or under the .razor file when that component has no code-behind.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <!--
  Probing for a Blazor parent costs a file system hit per snapshot file, so it is only done in
  projects that contain razor files. A code behind is included in that, since a test class can sit
  in one without the project holding the matching .razor.
  -->
  <ItemGroup Condition="('$(DisableVerifyFileNesting)' != 'true') And $(Language) == 'C#'">
    <VerifyRazorFile Include="**\*.razor;**\*.razor.cs" Exclude="$(DefaultItemExcludes);$(DefaultExcludesInProjectFolder)" />
  </ItemGroup>
  <PropertyGroup Condition="('$(DisableVerifyFileNesting)' != 'true')">
    <VerifyRazorFileCount>@(VerifyRazorFile->Count())</VerifyRazorFileCount>
  </PropertyGroup>
  <!--
  The SDK has already globbed the snapshots into None, so the metadata is applied with an Update.
  Adding a second item for a file the SDK holds would leave it in None twice, and anything that
  copies None into Content (eg DotNetProjectFile.Analyzers) then fails the build with NETSDK1022.
  The Include only picks up snapshots the SDK did not, such as when default items are disabled.
  -->
  <ItemGroup Condition="('$(DisableVerifyFileNesting)' != 'true')">
    <None Include="**\*.received.*;**\*.verified.*" Exclude="@(None);$(DefaultItemExcludes);$(DefaultExcludesInProjectFolder)" Condition="$(Language) == 'C#' Or $(Language) == 'VB'" />
    <None Update="**\*.received.*;**\*.verified.*" Condition="$(Language) == 'C#'">
      <ParentFile>$([System.String]::Copy('%(FileName)').Split('.')[0].Split('(')[0])</ParentFile>
      <ParentExtension>.cs</ParentExtension>
      <!-- A Blazor component keeps its code in a .razor.cs code-behind, or in the .razor file itself -->
      <ParentExtension Condition="'$(VerifyRazorFileCount)' != '0' And Exists('$(MSBuildProjectDirectory)\%(RelativeDir)%(ParentFile).razor.cs')">.razor.cs</ParentExtension>
      <ParentExtension Condition="'$(VerifyRazorFileCount)' != '0' And '%(ParentExtension)' == '.cs' And !Exists('$(MSBuildProjectDirectory)\%(RelativeDir)%(ParentFile).cs') And Exists('$(MSBuildProjectDirectory)\%(RelativeDir)%(ParentFile).razor')">.razor</ParentExtension>
      <DependentUpon>%(ParentFile)%(ParentExtension)</DependentUpon>
    </None>
    <None Update="**\*.received.*;**\*.verified.*" Condition="$(Language) == 'VB'">
      <ParentFile>$([System.String]::Copy('%(FileName)').Split('.')[0].Split('(')[0])</ParentFile>
      <DependentUpon>%(ParentFile).vb</DependentUpon>
    </None>
  </ItemGroup>
</Project>

^{snippet source | anchor}

To opt out of this feature, include the following in the project file:

<PropertyGroup>
  <DisableVerifyFileNesting>true</DisableVerifyFileNesting>
</PropertyGroup>

Media

Blogs

• Verify.Cli - Snapshot testing without tests - David Gardiner (21 Jul 2025)
• Snapshot testing .NET code with Verify - David Gardiner (21 Jul 2025)
• Library: Verify - Snapshot Testing - Simplify Complex Object Testing (2 Jan 2025)
• Snapshot Testing in .NET with Verify - Khalid Abuhakmeh (12 Jul 2024)
• Snapshot testing in C# with Verify - Tim Deschryver (21 Feb 2024)
• Snapshot Testing in C# - William Rees (13 Feb 2024)
• I want to do a snapshot test with C# (26 Dec 2023)
• I REGRET Not Telling Dave Farley THIS about Approval Testing - Emily Bache (27 Sep 2023)
• Today’s random F# code: Using Verify to prevent breaking changes in stored data - Urs Enzler (31 Mar 2023)
• Compare object values in xUnit C# with Verify - Pierre Belin (18 Nov 2022)
• Unit testing assertions are now easier than ever with Verify Snapshot tool - Rana Krishnrajsinh (5 Nov 2022)
• The easiest way to Unit Test with Verify in C# - Tomasz Juszczak (6 Sep 2022)
• Snapshot testing Verify.MongoDB: David Gardiner (31 Mar 2022)
• Testing an incremental generator with snapshot testing (14 Dec 2021)
• 5 helpful Nuget package for Unit Testing in .NET (16 Oct 2021)
• Snapshot Testing with Verify: Carl Franklin’s Blazor Train (3 Apr 2020)
• Verify: Snapshot Testing for C# (23 Nov 2020)

Podcasts

• Accessibilité, Azure Storage Action, Golden Master et Agentic AI (15 Jan 2025)
• Adventures in .NET: Mastering Dotnet Testing: Using Verify to Minimize Assertions (2 Jul 2024)
• Unhandled Exception podcast: Snapshot Testing (26 Nov 2021)
• Snapshot Testing with Verify - Dan Clarke (10 Dec 2021)

Videos

• Testing complex data with Verify - Lars Furu Kjelsaas (9 Jul 2025)
• The Only Type of Testing U Need - Nick Chapsas (12 Nov 2024)
• Introduction to Snapshot testing and using Verify.Xunit - Betatalks (11 Oct 2023)
• The Way to Test Legacy Code in C# - Gui Ferreira (19 Sep 2023)
• Snapshot Testing in .NET with Verify - Dan Clarke (21 Jul 2022)
• Testing C# code reliably by freezing it in time - Nick Chapsas (1 Aug 2022)
• 5 open source .NET projects that deserve more attention (9 Sep 2021)
• OSS Power-Ups: Verify (14 Jul 2021)
• Verify Xunit Intro (26 Apr 2020)

Plugins

• Verify.AngleSharp: Html verification utilities via AngleSharp.
• Verify.AspNetCore: Verification of AspNetCore bits.
• Verify.Aspose: Verification of documents (pdf, docx, xlsx, and pptx) via Aspose.
• Verify.Assertions: Extends Verify to allow an assertion callback. This enables using assertion libraries to interrogate during serialization.
• Verify.AustralianProtectiveMarkings: Verification of AustralianProtectiveMarkings.
• Verify.Avalonia: Verification of Avalonia UIs.
• Verify.Blazor: Verification of Blazor Component Blazor rendering.
• Verify.Bunit: Verification of Blazor Component via bunit.
• Verify.Brighter: Verification of Brighter bits.
• Verify.Cli: Command line tool for verifying files (outside of unit tests).
• Verify.CommunityToolkit.Mvvm: Verification of CommunityToolkit.Mvvm.
• Verify.Cosmos: Verification of Azure CosmosDB.
• Verify.ClosedXml: Verification of Excel documents via ClosedXml.
• Verify.CsvHelper: Verification of CSVs via CsvHelper.
• Verify.Diagnostics: Verification of System.Diagnostics.Activity types.
• Verify.OpenTelemetry: Verification of OpenTelemetry types.
• Verify.DocNet: Verification of pdfs via DocNet.
• Verify.EmailPreviewServices: Verification of html emails via EmailPreviewServices.
• Verify.EntityFramework: Verification of EntityFramework bits.
• Verify.FakeItEasy: Verification of FakeItEasy bits.
• Verify.Flurl: Verification of Flurl bits.
• Verify.GraphQL: Verification of GraphQL.NET bits.
• Verify.HeadlessBrowsers: Verification of Web UIs using Playwright, Puppeteer Sharp, or Selenium.
• Verify.Http: Verification of Http bits.
• Verify.ICSharpCode.Decompiler: Comparison of assemblies and types via ICSharpCode.Decompiler.
• Verify.ImageHash: Comparison of images via ImageHash.
• Verify.ImageSharp.Compare: Verification and comparison of images via Codeuctivity.ImageSharp.Compare.
• Verify.ImageMagick: Verification and comparison of images via Magick.NET.
• Verify.ImageSharp: Verification of images via ImageSharp.
• Verify.TestableIO.System.IO.Abstractions: Verification of TestableIO.System.IO.Abstractions.
• Verify.MailMessage: Verification of MailMessage and related types.
• YellowDogMan.Verify.Marshaling: Verification of Struct Marshaling.
• Verify.MassTransit: Support for MassTransit test helpers.
• Verify.MicrosoftLogging: Verify MicrosoftLogging.
• Verify.Mockly: Verification of Mockly bits.
• Verify.MongoDB: Verification of MongoDB bits.
• Verify.Moq: Verification of Moq bits.
• Verify.NodaTime: Support for NodaTime.
• Verify.NewtonsoftJson: Support for converting Newtonsoft.Json types (JObject and JArray).
• Verify.NServiceBus: Verify NServiceBus Test Contexts.
• Verify.NSubstitute: Support for NSubstitute types.
• Verify.Nupkg: Verification of NuGet .nupkg files.
• Verify.OfficeIMO: Verification of Word, Excel, PowerPoint, Visio, PDF, OpenDocument, RTF, EPUB, email and other documents via OfficeIMO.
• Verify.OpenXml: Verification of Excel documents via OpenXML.
• Verify.Pandoc: Verification of documents via PandocNet.
• Verify.PdfPig: Verification of pdfs via PdfPig.
• Verify.ParametersHashing: Extends Verify to allow hashing of parameters to mitigate long file names.
• Verify.Phash: Comparison of images via Phash.
• Verify.Quibble: Comparison of objects via Quibble.
• Verify.QuestPDF: Verification of pdf documents via QuestPDF.
• Verify.RavenDb: Verification of RavenDb bits.
• Verify.SendGrid: Verification of SendGrid.
• Verify.Sep: Verification of CSVs via Sep bits.
• Verify.Serilog: Verification of Serilog bits.
• YellowDogMan.Verify.ssimulacra2: Verification and comparison of images via ssimulacra2.
• Verify.SqlServer: Verification of SqlServer bits.
• Verify.SourceGenerators: Verification of C# Source Generators.
• Verify.SystemJson: Support for converting System.Text.Json types.
• Verify.Terminal: A dotnet tool for managing Verify snapshots.
• Verify.Ulid: Enable scrubbing of Universally Unique Lexicographically Sortable Identifiers via the Ulid package.
• Verify.NUlid: Enable scrubbing of Universally Unique Lexicographically Sortable Identifiers via NUlid package.
• Verify.WinForms: Verification of WinForms UIs.
• Verify.Xamarin: Verification of Xamarin UIs.
• Verify.Xaml: Verification of Xaml UIs.
• Spectre.Verify.Extensions: Add an attribute driven file naming convention to Verify.
• Verify.Sylvan.Data.Excel: Verification of Excel documents via Sylvan.Data.Excel.
• Verify.Syncfusion: Verification of documents (pdf, docx, xlsx, and pptx) via Syncfusion File Formats.
• Verify.Wolverine:Verifiable test context for Wolverine.
• Verify.Yaml: Support for YamlDotNet types.
• Verify.ZeroLog: Verifiable test context for ZeroLog.

TestMu AI

Browser testing via

More Documentation

• Clipboard
• Compared to assertions
• Verify options
• AutoVerify
• VerifyDirectory
• VerifyZip
• VerifyFile
• VerifyXml
• Serializer Settings
  • Obsolete members
  • Guids
  • Dates
  • Scrubbing
  • Solution Discovery
  • Counter
  • Members that throw
  • Ordering
  • Encoding
  • JsonAppender
  • Type to string mapping
• File naming
• AppendFile
• Parameterised tests
  • NUnit
  • Xunit V3
  • MSTest
  • TUnit
  • Fixie
  • Expecto
• Combinations
• Named Tuples
• Diff Engine
• Diff Tools
• Diff Tool Order
• Custom Diff Tool
• Using anonymous types
• Verifying binary data
• Newline tolerance
• Inline Snapshots
• Exception Message Format
• Build server
• Kill process locking file
• Comparers
• Converters
  • Paged documents
• Context
• Recording
• Explicit Targets
• TempDirectory
• TempFile
• FSharp Usage
• Compared to ApprovalTests
• AI Usage
• Plugins
• Open Source Maintenance Fee

Icon

Helmet designed by Leonidas Ikonomou from The Noun Project.