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.
We just shipped prerelease builds of core framework (3.0.0-pre.15) and analyzers (1.23.0-pre.3).
This is a major version update with breaking changes. Check the release notes for more information.
https://xunit.net/releases/v3/3.0.0-pre.15
https://xunit.net/releases/analyzers/1.23.0-pre.3
We just shipped core framework v3 2.0.3, analyzers 1.22.0, and Visual Studio adapter 3.1.1.
Check the release notes for new features and bugs fixed.
https://xunit.net/releases/v3/2.0.3
https://xunit.net/releases/analyzers/1.22.0
https://xunit.net/releases/visualstudio/3.1.1
We just shipped core framework v3 2.0.2 and Visual Studio adapter 3.1.0.
Check the release notes for new features and bugs fixed.
Note: The Visual Studio adapter has moved up to .NET 8 (from .NET 6).
https://xunit.net/releases/v3/2.0.2
https://xunit.net/releases/visualstudio/3.1.0
We have a prototype of the API documentation online: https://api.xunit.net/
We're not sure if it will live on a separate URL forever, but until the main site is rebuilt with DocFX, this is how it has to be for now.
Feedback welcome!
We just shipped core framework v3 2.0.1 and source analyzers 1.21.0.
Check the release notes for new features and bugs fixed.
https://xunit.net/releases/v3/2.0.1
https://xunit.net/releases/analyzers/1.21.0
Holy crap! I just noticed we're up to 130 unit test suites in @pidgin 3 now! Compare that to the 7 suites we have in Pidgin 2!
This is what we've been talking about when we've been saying that we're making the code easier to maintain. The code has been reworked so that we can actually unit test way more of it and we will continue to add more tests as we move forward!
We just shipped core framework v3 2.0.0.
This contains breaking changes, so the release notes are rather more detailed than normal.
Release notes: https://xunit.net/releases/v3/2.0.0
More thoughts about test parallelism as it involves the starting/finished message pairs for test collections, test classes, and test methods.
If you're a runner author, do you use these messages? Can we just remove them?
Provide thoughts here: https://github.com/xunit/xunit/discussions/3164#discussioncomment-12217024
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 are considering changing some of the options for the ways tests run in parallel against one another. Please read this and add your thoughts. Thanks!
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?
We have just shipped new builds of Core Framework v3, Analyzers, and Visual Studio adapter.
Release notes:
https://xunit.net/releases/v3/1.1.0
https://xunit.net/releases/analyzers/1.20.0
https://xunit.net/releases/visualstudio/3.0.2
We are permanently enabling support for Span/Memory and immutable collections in the assertion library, removing the XUNIT_SPAN and XUNIT_IMMUTABLE_COLLECTIONS flags for source-based consumers.
You may need to add NuGet package references to System.Collections.Immutable and/or System.Memory.
If you are writing individual unittests, you may be doing testing wrong.
I finally #parameterized all the #python #unittest for my deployment tool.
This is the way testing should be done.
The way testing is taught, with single unit tests is very misleading.
With parameterized tests, I can automatically test a significant portion of the input space of function or program.
We are planning to bump up the minimum version of .NET from 6 to 8 in the 2.0 release. The 1.x releases will continue to allow targeting .NET 6.
There is no timeline yet for this release.
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
Do you think it's weird that v3 test projects are stand-alone executables? You're not alone. Here is a brief history behind the decision.
https://github.com/xunit/xunit/issues/3139#issuecomment-2611568692
DevelopersIO 
