fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#unittest

1 post1 participant0 posts today
Brad Wilson<p>Happy birthday <span class="h-card" translate="no"><a href="https://dotnet.social/@xunit" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>xunit</span></a></span> </p><p>Version 1.0 was released on July 24, 2007. You're old enough to vote now.</p><p><a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a></p>
xUnit.net<p>"Microsoft Testing Platform is cool!" by Tomasz Cielecki <span class="h-card" translate="no"><a href="https://fosstodon.org/@Cheesebaron" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Cheesebaron</span></a></span> <a href="https://blog.ostebaronen.dk/2025/07/ms-test-platform-is-cool.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.ostebaronen.dk/2025/07/ms</span><span class="invisible">-test-platform-is-cool.html</span></a> <a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a></p>
Danny Whitt<p>Using <a href="https://mastodon.social/tags/claude" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>claude</span></a> to write <a href="https://mastodon.social/tags/flutter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flutter</span></a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> code in a single sit down session.</p><p>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">#<span>aihallucination</span></a> (a made-up foundation class) it easily achieved &gt;50% pass/fail and &gt;70% <a href="https://mastodon.social/tags/coverage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coverage</span></a>.</p><p>Impressive or not?</p><p>EDIT: And, yes, this absolutely included reading/code-reviewing all generated code before running the tests.</p><p><a href="https://mastodon.social/tags/ama" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ama</span></a> <a href="https://mastodon.social/tags/codinglife" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codinglife</span></a></p>
xUnit.net<p>We just shipped Visual Studio adapter 3.1.3.</p><p>This is a bug fix release to address a failure case when running xUnit.net v2 tests (which was introduced in 3.1.0).</p><p><a href="https://xunit.net/releases/visualstudio/3.1.3" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/visualstudi</span><span class="invisible">o/3.1.3</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
xUnit.net<p>We just shipped Core Framework v3 3.0.0, Analyzers 1.23.0, and Visual Studio adapter 3.1.2.</p><p>Check the release notes for breaking changes, new features, and bugs fixed.</p><p><a href="https://xunit.net/releases/v3/3.0.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/3.0.0</span><span class="invisible"></span></a><br><a href="https://xunit.net/releases/analyzers/1.23.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/analyzers/1</span><span class="invisible">.23.0</span></a><br><a href="https://xunit.net/releases/visualstudio/3.1.2" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/visualstudi</span><span class="invisible">o/3.1.2</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
xUnit.net<p>We just shipped a new prerelease build of the core framework (3.0.0-pre.40).</p><p>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).</p><p><a href="https://xunit.net/releases/v3/3.0.0-pre.40" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/v3/3.0.0-pr</span><span class="invisible">e.40</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
xUnit.net<p>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...</p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
Python Rennes<p>une bibliothèque pour mocker les ressources <a href="https://social.breizhcamp.org/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AWS</span></a> utilisées dans le code de production <a href="https://social.breizhcamp.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> que vous testez (S3, par exemple) : <a href="https://github.com/getmoto/moto" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/getmoto/moto</span><span class="invisible"></span></a></p><p>La page <a href="https://github.com/getmoto/moto/blob/master/docs/docs/getting_started.rst" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/getmoto/moto/blob/m</span><span class="invisible">aster/docs/docs/getting_started.rst</span></a> documente comment écrire les tests (<a href="https://social.breizhcamp.org/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pytest</span></a>, <a href="https://social.breizhcamp.org/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></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).</p>
Data Science<p>{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"><span class="invisible">https://</span><span class="ellipsis">blog.r-hub.io/2020/11/18/testt</span><span class="invisible">hat-utility-belt/</span></a> <a href="https://genomic.social/tags/rstats" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rstats</span></a> <a href="https://genomic.social/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> <a href="https://genomic.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> <a href="https://genomic.social/tags/testthat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testthat</span></a></p>
TSM at Work<p>I wanted a <a href="https://noc.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> to prove that adjusting the system <a href="https://noc.social/tags/cryptograhy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptograhy</span></a> <a href="https://noc.social/tags/policy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>policy</span></a> would achieve the intended outcome. 🧵</p>
xUnit.net<p>We just shipped a new prerelease build of the core framework (3.0.0-pre.25).</p><p>This includes new breaking changes since last week's prerelease. Please check the release notes for more information.</p><p><a href="https://xunit.net/releases/v3/3.0.0-pre.25" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/v3/3.0.0-pr</span><span class="invisible">e.25</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
ENEP Linuxoid<p>The 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.</p><p><a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://mastodon.social/tags/refactoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>refactoring</span></a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> <a href="https://mastodon.social/tags/kde" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kde</span></a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.social/tags/CPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CPP</span></a> <a href="https://mastodon.social/tags/Qt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Qt</span></a></p>
Allan Svelmøe Hansen<p>So made a source generator - ended up rather complex. <br>But I find unit testing it very tedious when verifying the generated output via Verify. </p><p>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</p><p><a href="https://hachyderm.io/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotnet</span></a> <a href="https://hachyderm.io/tags/sourcegenerator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sourcegenerator</span></a> <a href="https://hachyderm.io/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a></p>
xUnit.net<p>We just shipped prerelease builds of core framework (3.0.0-pre.15) and analyzers (1.23.0-pre.3).</p><p>This is a major version update with breaking changes. Check the release notes for more information.</p><p><a href="https://xunit.net/releases/v3/3.0.0-pre.15" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/v3/3.0.0-pr</span><span class="invisible">e.15</span></a><br><a href="https://xunit.net/releases/analyzers/1.23.0-pre.3" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/analyzers/1</span><span class="invisible">.23.0-pre.3</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
xUnit.net<p>We just shipped core framework v3 2.0.3, analyzers 1.22.0, and Visual Studio adapter 3.1.1.</p><p>Check the release notes for new features and bugs fixed.</p><p><a href="https://xunit.net/releases/v3/2.0.3" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/2.0.3</span><span class="invisible"></span></a><br><a href="https://xunit.net/releases/analyzers/1.22.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/analyzers/1</span><span class="invisible">.22.0</span></a><br><a href="https://xunit.net/releases/visualstudio/3.1.1" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/visualstudi</span><span class="invisible">o/3.1.1</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
Fake Scrum Stats Memes & Humor<p><a href="https://techhub.social/tags/scrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scrum</span></a> <a href="https://techhub.social/tags/scrumteam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scrumteam</span></a> <a href="https://techhub.social/tags/dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dev</span></a> <a href="https://techhub.social/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developer</span></a> <a href="https://techhub.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://techhub.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTesting</span></a> <a href="https://techhub.social/tags/unittests" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittests</span></a> <a href="https://techhub.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> <a href="https://techhub.social/tags/unittestcoverage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittestcoverage</span></a> <a href="https://techhub.social/tags/unittestingmuch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittestingmuch</span></a> <a href="https://techhub.social/tags/Meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Meme</span></a> <a href="https://techhub.social/tags/memes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memes</span></a> <a href="https://techhub.social/tags/Humor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Humor</span></a> <a href="https://techhub.social/tags/humour" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>humour</span></a></p>
Brian Allbee<p>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.</p><p><a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a></p><p><a href="https://goblinfish-code.blogspot.com/2025/05/when-not-to-mock-or-patch.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">goblinfish-code.blogspot.com/2</span><span class="invisible">025/05/when-not-to-mock-or-patch.html</span></a></p>
xUnit.net<p>We just shipped core framework v3 2.0.2 and Visual Studio adapter 3.1.0.</p><p>Check the release notes for new features and bugs fixed.</p><p>Note: The Visual Studio adapter has moved up to .NET 8 (from .NET 6).</p><p><a href="https://xunit.net/releases/v3/2.0.2" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/2.0.2</span><span class="invisible"></span></a><br><a href="https://xunit.net/releases/visualstudio/3.1.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/releases/visualstudi</span><span class="invisible">o/3.1.0</span></a></p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>
kalvn<p>Quelques bonnes pratiques pour tester votre application Node.js.</p><p>🔗 <a href="https://github.com/goldbergyoni/nodejs-testing-best-practices#readme" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/goldbergyoni/nodejs</span><span class="invisible">-testing-best-practices#readme</span></a></p><p><a href="https://mastodon.xyz/tags/nodejs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nodejs</span></a> <a href="https://mastodon.xyz/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> <a href="https://mastodon.xyz/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a></p>
xUnit.net<p>We have a prototype of the API documentation online: <a href="https://api.xunit.net/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">api.xunit.net/</span><span class="invisible"></span></a></p><p>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.</p><p>Feedback welcome!</p><p><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TDD</span></a></p>