MastodonTech.de

xUnit.netThe last core framework release was July 13. We definitely have enough for a new release next week. If you're so inclined, maybe pick up a CI build and test it before we ship and/or raise awareness of anything you want fixed. <a href="https://xunit.net/docs/using-ci-builds" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/docs/using-ci-builds</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

Brad WilsonThe amount of difficulty in making the <a href="https://dotnet.social/@xunit" class="u-url mention" rel="nofollow noopener" target="_blank">@xunit</a> assertion library work in Native AOT has me thinking about whether it needs a complete redesign for those types of projects.Trying to shove 50 things into `Assert.Equal` and figure out what you meant at runtime is definitely not the right design for AOT. It's not necessarily a great design at all, but there's where it's been for 18 years.<a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a>

xUnit.netGiven that xUnit.net runs tests in random order by default, would changing the randomization order (in order to fix a bug) just be considered a bug fix or a breaking change?Asking for a SemVer.<a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

Brad WilsonHappy birthday <a href="https://dotnet.social/@xunit" class="u-url mention" rel="nofollow noopener" target="_blank">@xunit</a> Version 1.0 was released on July 24, 2007. You're old enough to vote now.<a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a>

xUnit.net"Microsoft Testing Platform is cool!" by Tomasz Cielecki <a href="https://fosstodon.org/@Cheesebaron" class="u-url mention" rel="nofollow noopener" target="_blank">@Cheesebaron</a> <a href="https://blog.ostebaronen.dk/2025/07/ms-test-platform-is-cool.html" rel="nofollow noopener" translate="no" target="_blank">https://blog.ostebaronen.dk/2025/07/ms-test-platform-is-cool.html</a> <a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a>

Danny WhittUsing <a href="https://mastodon.social/tags/claude" class="mention hashtag" rel="nofollow noopener" target="_blank">#claude</a> to write <a href="https://mastodon.social/tags/flutter" class="mention hashtag" rel="nofollow noopener" target="_blank">#flutter</a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a> code in a single sit down session.Without no logical edits and only sparse missing imports and only a single <a href="https://mastodon.social/tags/aihallucination" class="mention hashtag" rel="nofollow noopener" target="_blank">#aihallucination</a> (a made-up foundation class) it easily achieved >50% pass/fail and >70% <a href="https://mastodon.social/tags/coverage" class="mention hashtag" rel="nofollow noopener" target="_blank">#coverage</a>.Impressive or not?EDIT: And, yes, this absolutely included reading/code-reviewing all generated code before running the tests.<a href="https://mastodon.social/tags/ama" class="mention hashtag" rel="nofollow noopener" target="_blank">#ama</a> <a href="https://mastodon.social/tags/codinglife" class="mention hashtag" rel="nofollow noopener" target="_blank">#codinglife</a>

xUnit.netWe 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).<a href="https://xunit.net/releases/visualstudio/3.1.3" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/visualstudio/3.1.3</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

xUnit.netWe 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.<a href="https://xunit.net/releases/v3/3.0.0" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/3.0.0</a> <a href="https://xunit.net/releases/analyzers/1.23.0" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.23.0</a> <a href="https://xunit.net/releases/visualstudio/3.1.2" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/visualstudio/3.1.2</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

xUnit.netWe 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).<a href="https://xunit.net/releases/v3/3.0.0-pre.40" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/3.0.0-pre.40</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

xUnit.netJust 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...<a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

Python Rennesune bibliothèque pour mocker les ressources <a href="https://social.breizhcamp.org/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> utilisées dans le code de production <a href="https://social.breizhcamp.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> que vous testez (S3, par exemple) : <a href="https://github.com/getmoto/moto" rel="nofollow noopener" translate="no" target="_blank">https://github.com/getmoto/moto</a>La page <a href="https://github.com/getmoto/moto/blob/master/docs/docs/getting_started.rst" rel="nofollow noopener" translate="no" target="_blank">https://github.com/getmoto/moto/blob/master/docs/docs/getting_started.rst</a> documente comment écrire les tests (<a href="https://social.breizhcamp.org/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#pytest</a>, <a href="https://social.breizhcamp.org/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a>) et donne quelques conseils pour écrire du code de production plus facile à tester (en ce qui concerne les interactions avec boto3, le client vers les services AWS).

Data Science{testthat} is great for automatic testing. Here are some tricks for the heavy user: <a href="https://blog.r-hub.io/2020/11/18/testthat-utility-belt/" rel="nofollow noopener" translate="no" target="_blank">https://blog.r-hub.io/2020/11/18/testthat-utility-belt/</a> <a href="https://genomic.social/tags/rstats" class="mention hashtag" rel="nofollow noopener" target="_blank">#rstats</a> <a href="https://genomic.social/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> <a href="https://genomic.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a> <a href="https://genomic.social/tags/testthat" class="mention hashtag" rel="nofollow noopener" target="_blank">#testthat</a>

xUnit.netWe 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.<a href="https://xunit.net/releases/v3/3.0.0-pre.25" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/3.0.0-pre.25</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

ENEP LinuxoidThe class functionality of the class then drinks the squeaks of tests and the starting of the refactoring, bug fixes and the next tests until all tests will not begin to work correctly.<a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://mastodon.social/tags/refactoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#refactoring</a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a> <a href="https://mastodon.social/tags/kde" class="mention hashtag" rel="nofollow noopener" target="_blank">#kde</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/CPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPP</a> <a href="https://mastodon.social/tags/Qt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Qt</a>

Allan Svelmøe HansenSo 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<a href="https://hachyderm.io/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://hachyderm.io/tags/sourcegenerator" class="mention hashtag" rel="nofollow noopener" target="_blank">#sourcegenerator</a> <a href="https://hachyderm.io/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a>

xUnit.netWe 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.<a href="https://xunit.net/releases/v3/3.0.0-pre.15" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/3.0.0-pre.15</a> <a href="https://xunit.net/releases/analyzers/1.23.0-pre.3" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.23.0-pre.3</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

xUnit.netWe 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.<a href="https://xunit.net/releases/v3/2.0.3" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/2.0.3</a> <a href="https://xunit.net/releases/analyzers/1.22.0" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.22.0</a> <a href="https://xunit.net/releases/visualstudio/3.1.1" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/visualstudio/3.1.1</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

Fake Scrum Stats Memes & Humor<a href="https://techhub.social/tags/scrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#scrum</a> <a href="https://techhub.social/tags/scrumteam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scrumteam</a> <a href="https://techhub.social/tags/dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#dev</a> <a href="https://techhub.social/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a> <a href="https://techhub.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://techhub.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://techhub.social/tags/unittests" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittests</a> <a href="https://techhub.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a> <a href="https://techhub.social/tags/unittestcoverage" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittestcoverage</a> <a href="https://techhub.social/tags/unittestingmuch" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittestingmuch</a> <a href="https://techhub.social/tags/Meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meme</a> <a href="https://techhub.social/tags/memes" class="mention hashtag" rel="nofollow noopener" target="_blank">#memes</a> <a href="https://techhub.social/tags/Humor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Humor</a> <a href="https://techhub.social/tags/humour" class="mention hashtag" rel="nofollow noopener" target="_blank">#humour</a>

Brian AllbeeAs 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.<a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a><a href="https://goblinfish-code.blogspot.com/2025/05/when-not-to-mock-or-patch.html" rel="nofollow noopener" translate="no" target="_blank">https://goblinfish-code.blogspot.com/2025/05/when-not-to-mock-or-patch.html</a>

xUnit.netWe 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).<a href="https://xunit.net/releases/v3/2.0.2" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/v3/2.0.2</a> <a href="https://xunit.net/releases/visualstudio/3.1.0" rel="nofollow noopener" translate="no" target="_blank">https://xunit.net/releases/visualstudio/3.1.0</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#Unittest