No output with TUnit

[tacoWanneeJama]

Preamble

Where relevant, ensure you are using the current stable versions on your development stack. For example:

• Visual Studio
• .Net 10
• C#

Describe the bug

When I update the Verify.TUnit from version 31.20.0 to a newer version, no target.verified.txt and target.received.txt are generated when I use DiffPlex. If I diasable Verify.DiffPlex the problem doe not occur.
I am usingVerify.DiffPlex 3.3.0.
Everything works fine with Verify.TUnit version 31.20.0

Minimal Repro

<PackageVersion Include="TUnit" Version="1.59.0" />
<PackageVersion Include="Verify.DiffPlex" Version="3.3.0" />
<PackageVersion Include="Verify.TUnit" Version="31.20.0" />

    [ModuleInitializer]
    public static void Initialize()
    {
        _verifySettings.UseUniqueDirectory();
        if (!VerifyDiffPlex.Initialized)
            VerifyDiffPlex.Initialize(VerifyTests.DiffPlex.OutputType.Compact);
        Verifier.UseSourceFileRelativeDirectory("Snapshots");
    }

[SimonCropp]

can u share a zipped minimal repro

[tacoWanneeJama]

I am working on a working example, but I have to dig deeper....

[tacoWanneeJama]

I have made a test project with the same problem: https://github.com/tacoWanneeJama/BlazorBugTestApp.git.
When you run it the second time it crashes with an error that is caused by missing output.
When you change the Verify.TUnit to version 31.20.0 this error does not occur.

[SimonCropp]

can you reduce that down to a minimal repro.

eg it should be only one project and only pull in the required nugets to reproduce the problem

[tacoWanneeJama]

Here it is:
https://github.com/tacoWanneeJama/BlazorBugUnittest.git

[tacoWanneeJama]

Is this simple enough to reproduce?

[SimonCropp]

@tacoWanneeJama it is. thanks

[SimonCropp]

This isn't a Verify.DiffPlex bug — it's a line-endings issue in the snapshot files.

What's happening

Your .gitattributes has * text=auto (line 4) and git has core.autocrlf=true, so although the files are stored as LF in the repo, they land in your working tree as CRLF on a Windows checkout. Verify requires verified files to use LF — see Text file settings.

Verify 31.21.0 made that a hard error. 31.20.0 tolerated CRLF, which is exactly why it "works fine on 31.20.0". Running your repro unchanged, varying only the Verify.TUnit version:

Verify.TUnit	Result with your verified files
31.20.0	passes
31.21.0 – 31.24.1	throws

The error is:

Verified file must use \n line endings, but it contains a \r (carriage return).
Path: ...\target.verified.txt
See https://github.com/verifytests/verify#text-file-settings

Why you see no output

That check throws inside Comparer.Text, which runs before the .received.txt is written. The run aborts with Failed to compare files: and no received file is ever produced. That's your "no target.received.txt is generated" symptom — the file isn't missing, it's never reached.

Why it isn't DiffPlex

The throw happens before the string comparer is invoked, so DiffPlex never runs at all. I confirmed this by removing VerifyDiffPlex.Initialize() from your repro entirely — identical error, same missing output.

The fix

1. Add to .gitattributes (see Text file settings):

*.verified.txt text eol=lf working-tree-encoding=UTF-8

2. Commit it, then force git to re-check-out the files under the new rule:

git add .gitattributes
git commit -m "Add Verify text file settings"
git rm --cached -r .
git reset --hard

Your blobs are already LF, so there's nothing to re-normalize — this just makes them check out as LF instead of CRLF. Verify that with git ls-files --eol Snapshots — you want w/lf, not w/crlf.

3. Your verified files also have a trailing newline, which Verify doesn't write and git won't fix — it's in the committed content, and your editor is adding it on save. Add to .editorconfig:

[*.{received,verified}.{json,txt,xml}]
charset = utf-8-bom
end_of_line = lf
insert_final_newline = false

Then regenerate the snapshots — delete the target.verified.txt files, re-run, and accept the received output.

With the files checked out as LF and the trailing newline gone, both tests pass in your repro with DiffPlex enabled.

Unrelated, but it'll bite you next

The repro references Microsoft.NET.Test.Sdk and sets EnableMSTestRunner. TUnit is a Microsoft.Testing.Platform framework with no VSTest adapter, so IDE/dotnet test discovery finds nothing ("no tests in solution"), and on the .NET 10 SDK it hard-errors. Drop both, and add a global.json with:

{
  "test": {
    "runner": "Microsoft.Testing.Platform"
  }
}