#unitTest

Ukiah Danger SmithUkiahSmith
2026-01-19

I guess for me it is more about having a high level of confidence that the tests I run protect me from regressions.

Using mocks in strictly local tests seems to erode confidence. Where using mocks in integration tests gives me confidence to test full end to end tests.

Ænðr E. Feldstrawaeveltstra
2026-01-14

I spent some time writing up how to the creation and changing of database components in 's . It's useful in restricted environments that won't allow other development tools that normally could conduct unit tests.
patreon.com/posts/148232620

2026-01-14

We just shipped Core Framework v3 3.2.2 and Analyzers 1.27.0.

This includes new templates which default to Microsoft Testing Platform v2 and a new Native AOT compatible assertions package (plus bug fixes).

xunit.net/releases/v3/3.2.2
xunit.net/releases/analyzers/1

#DotNet #CSharp #FSharp #UnitTest #TDD

Brad Wilsonbradwilson
2026-01-10

Success! 🎉 The runner-side of @xunit has been made native AOT compatible, resulting in our ability publish a native multi-assembly runner.

This runner is only able to run v3 projects (.NET or .NET Framework). It will definitely *never* be able to run v1 or v2 tests, since those require a runtime environment that's not possible in Native AOT.

Building the native AOT console runner, running a (non-native AOT) v3 .NET 8 test project. The executable is stand-alone and roughly 8.5MB (compiled for x86_64 Windows).
Olivier Mehanishtrom@piaille.fr
2026-01-09

Damn you, ImageMagick!

#python #imageMagick #unittest

Screenshot of some Python code:

```
mock_landing_assessment = mock.MagickMock()
mock_landing_assessment.lando_user = user_without_perms   
```

The LSP also complains that `"MagickMock" is not a known attribute of module "unittest.mock"`
2026-01-02

When we release 4.0, we will be switching the default Microsoft.Testing.Platform version from v1 to v2. This may cause compatibility issues with any dependent packages that are built for v1, hence waiting for a major version shift.

We will continue to support your option to choose v1.

#DotNet #UnitTest

2025-12-30

We are updating the `xunit3` project template in the next release:

* Offering a switch to choose MTP version: v2 (default), v1, or off
* Will not include VSTest support (`xunit.runner.visualstudio`) unless MTP is off

This updates the defaults for new projects without breaking backward compatibility for existing projects using the MTP v1 default.

#DotNet #UnitTest

2025-12-30

New doc page: Using Microsoft.Testing.Platform with xUnit.net v2. xunit.net/docs/getting-started #DotNet #UnitTest

2025-12-08
Der Nebel hängt heute dicht über Passau – graues, gleichmäßiges Weiß, alles leicht feucht. Ich sitze unterm Balkonvordach, der Laptop läuft, das Oszilloskop wärmt sich langsam auf. Die Messkiste ist trocken unter der Plane, Kabel sauber fixiert. Perfekter Vormittag, um endlich die unschöne Baustelle in trace_agg.py abzuschließen. Ich hab den Unit‑Test nochmal angeworfen – diesmal mit acht repräsentativen Trace‑Exports. Jedes File enthält im Schnitt etwa 62 […]
2025-12-12
Bedeckt, knapp sechs Grad – ich sitz unter dem Vordach, der Laptop läuft warm, daneben blinkt das kleine Oszi‑Display. Letzter Check vorm Merge: die nachverifizierte Aggregation mit Integer‑Buckets. Der Fix war ja seit ein paar Tagen im Fokus, und heute hab ich ihn nochmal auf den synthetischen Trace‑Satz (N=8 Exporte) losgelassen. Ergebnis: sauber. Die Gesamtsumme blieb exakt bei 499, kein Off‑by‑3 mehr. 🤓 Der Vergleich zwischen alter Float‑Bucket‑Ausgabe und der neuen […]
2025-12-25

Youssef (of the Microsoft TestFx team) is working on a personal project to add support for Microsoft.Testing.Platform to v2 projects, for those who are not yet able to migrate to v3. github.com/Youssef1313/YTest.M #DotNet #UnitTest

2025-12-20

Is there interest in us shipping ready-made binaries of xunit.v3.runner.console (via the xunit.v3.runner.console NuGet package) that target .NET instead of .NET Framework? Which runtime IDs would you need to be supported? learn.microsoft.com/en-us/dotn #DotNet #UnitTest

2025-12-04

We are considering dropping support for Mono from the next major version. (It will likely continue to work, we just won't officially support it.)

Are you still using Mono to run tests? If so, on which OSes? #DotNet #UnitTest

Allan Svelmøe Hansensvelmoe@hachyderm.io
2025-12-04

After fighting with DevOps over testing some legacy time conversions; I managed to fail a unit test because I used a control date from before daylight saving was introduced, so my expected offset was incorrect :)

I feel old.

#dotnet #unittest #test

Dr. Marco Klement | Talkmaklem@leuchtstark.dev
2025-12-02

@riffraff I join on the question on test naming. I know a scheme with subject_onAction_expectedBehaviour, but that clashes with snake case (and gives warnings when running tests)

#rust #rustlang #test #tdd #unittest #namingthings

2025-11-28

We just shipped Core Framework v3 3.2.1 and Analyzers 1.26.0.

This is primarily a bug fix release. Check the release notes for more information.

xunit.net/releases/v3/3.2.1
xunit.net/releases/analyzers/1

#DotNet #CSharp #FSharp #UnitTest #TDD

2025-11-16

We're going to start pushing CI builds for 4.0.0, as we have two feature branches that require a major version bump already. There's no planned release date yet (not even a planned NuGet release yet), so no idea how long the branch will live.

#DotNet #CSharp #FSharp #UnitTest #TDD

2025-11-10

If you are using a test case orderer today (implementing `ITestCaseOrderer`), take a peek at this issue that wants to introduce `ITestClassOrderer` and `ITestMethodOrderer` and the impact it has on developers using test case orderers today. Feedback welcome! github.com/xunit/xunit/issues/

#DotNet #UnitTest #TDD

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst