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 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.
So made a source generator - ended up rather complex.
But I find unit testing it very tedious when verifying the generated output via Verify.
Is it not possible to load a class/instance as source in the testing, and use it as foundation for the generator. Instead of having to manually writing (and maintaining) the source as a string to then parse into a syntax tree to verify output? I mean it can generate on compile time, so why not at test? :D
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
As it turns out, there were some fundamental problems with the testing-strategy I had in mind for testing the PACT processes. That is, problems with how I'd planned to implement those tests, not with which tests needed to be implemented (at least not yet). Those issues took a bit of thinking through, and there were some interesting results from related investigation.
https://goblinfish-code.blogspot.com/2025/05/when-not-to-mock-or-patch.html
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
Quelques bonnes pratiques pour tester votre application Node.js.
🔗 https://github.com/goldbergyoni/nodejs-testing-best-practices#readme
Beyond the basics of Node.js testing. Including a super-comprehensive best practices list and an example app (April 2025) - goldbergyoni/nodejs-testing-best-practices
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!