Happy birthday @xunit
Version 1.0 was released on July 24, 2007. You're old enough to vote now.
Happy birthday @xunit
Version 1.0 was released on July 24, 2007. You're old enough to vote now.
"Microsoft Testing Platform is cool!" by Tomasz Cielecki https://blog.ostebaronen.dk/2025/07/ms-test-platform-is-cool.html #DotNet #UnitTest
Using #claude to write #flutter #unittest code in a single sit down session.
Without no logical edits and only sparse missing imports and only a single #aihallucination (a made-up foundation class) it easily achieved >50% pass/fail and >70% #coverage.
Impressive or not?
EDIT: And, yes, this absolutely included reading/code-reviewing all generated code before running the tests.
We just shipped Visual Studio adapter 3.1.3.
This is a bug fix release to address a failure case when running xUnit.net v2 tests (which was introduced in 3.1.0).
We just shipped Core Framework v3 3.0.0, Analyzers 1.23.0, and Visual Studio adapter 3.1.2.
Check the release notes for breaking changes, new features, and bugs fixed.
https://xunit.net/releases/v3/3.0.0
https://xunit.net/releases/analyzers/1.23.0
https://xunit.net/releases/visualstudio/3.1.2
We just shipped a new prerelease build of the core framework (3.0.0-pre.40).
There are no new breaking changes, so this will not reset our release clock for 3.0.0 (which should be in about a week).
Just a reminder that we only have roughly 10 more days of before we ship 3.0. If you've been putting off validating your tests and/or extensions with the latest prerelease, your time is running low...
{testthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat
We just shipped a new prerelease build of the core framework (3.0.0-pre.25).
This includes new breaking changes since last week's prerelease. Please check the release notes for more information.
Thinking about what an AOT version of @xunit would look like. I spent some time talking to @agocke last year about it so I have some thoughts.
It almost surely end up being a completely separate code base/package. No mixing and matching, because the internal design would be very different.
Top three things I think:
- .NET 8+ only (no .NET Framework)
- C# only (no F# or VB)
- No extensibility points (you get our Fact and Theory, you get our pipeline).
1/
We'd like to get some feedback on a change coming in 2.0.0 for Assert.Equal displays when doing collection comparisons. We've already made a change to make string comparisons better, but should we do it for all collection values?
Goodbye Michael Foord.
You will be missed.
- Nice write up by Nicholas Tollervey: https://ntoll.org/article/my-friend-michael/
- 2021 interview with him: https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord
It's release day!
We just shipped v2 Core Framework 2.5.0, Analyzers 1.2.0, and Visual Studio adapter 2.5.0. This release includes a bunch of quality of life improvements, bug fixes, and an overhauled assertion library that includes new assertions, new overloads, and much better (and most consistent) assertion failure messages.
Enjoy!
Release notes:
https://xunit.net/releases/v2/2.5.0
https://xunit.net/releases/analyzers/1.2.0
https://xunit.net/releases/visualstudio/2.5.0