Ruby.social

xUnit.netWe have a prototype of the API documentation online: <a href="https://api.xunit.net/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://api.xunit.net/</a>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!<a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

xUnit.netWe just shipped core framework v3 2.0.1 and source analyzers 1.21.0.Check the release notes for new features and bugs fixed.<a href="https://xunit.net/releases/v3/2.0.1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/v3/2.0.1</a> <a href="https://xunit.net/releases/analyzers/1.21.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.21.0</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

FlominatorHad an old <a href="https://genealysis.social/tags/unitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTest</a> in a legacy project failing for some time already, but didn't recognize it/bother. Now I figured out the reason: the English name for <a href="https://genealysis.social/tags/Turkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Turkey</a> returned by the operating system is meanwhile <a href="https://genealysis.social/tags/T%C3%BCrkiye" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Türkiye</a>, which doesn't match the old enum value Turkey anymore. <a href="https://genealysis.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> <a href="https://genealysis.social/tags/csharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csharp</a>

Gary "grim" KramlichHoly crap! I just noticed we're up to 130 unit test suites in <a href="https://fosstodon.org/@pidgin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pidgin</a> 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!<a href="https://mastodon.social/tags/Pidgin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pidgin</a> <a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://mastodon.social/tags/Maintainability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Maintainability</a> <a href="https://mastodon.social/tags/techdebt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#techdebt</a>

xUnit.netWe just shipped core framework v3 2.0.0.This contains breaking changes, so the release notes are rather more detailed than normal.Release notes: <a href="https://xunit.net/releases/v3/2.0.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/v3/2.0.0</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

Thiago BomfimIf you have many assertions, you can also use the SoftAssertions to test all the assertions and give all the results at once.Read more 👉 <a href="https://lttr.ai/ATQTo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lttr.ai/ATQTo</a><a href="https://mastodon.social/tags/test" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#test</a> <a href="https://mastodon.social/tags/unitest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitest</a> <a href="https://mastodon.social/tags/unitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTest</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> <a href="https://mastodon.social/tags/AssertJ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssertJ</a> <a href="https://mastodon.social/tags/assertions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assertions</a> <a href="https://mastodon.social/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a> <a href="https://mastodon.social/tags/developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developer</a>

xUnit.netMore 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: <a href="https://github.com/xunit/xunit/discussions/3164#discussioncomment-12217024" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/xunit/xunit/discussions/3164#discussioncomment-12217024</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

Brad WilsonA good first step.These tests (and xunit.v3.assert.aot) are compiled with <PublishAot>true</PublishAot>, but still being run normally (not via a published executable). It's hard for me to know how many *more* tests might fail after publishing, but that's quite a ways off.<a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://mastodon.social/tags/NativeAOT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NativeAOT</a>

Brad WilsonThinking about what an AOT version of <a href="https://dotnet.social/@xunit" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@xunit</a> would look like. I spent some time talking to <a href="https://hachyderm.io/@agocke" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@agocke</a> 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/<a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://mastodon.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://mastodon.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSharp</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

xUnit.netWe 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!<a href="https://github.com/xunit/xunit/discussions/3164" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/xunit/xunit/discussions/3164</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

xUnit.netWe'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?<a href="https://github.com/xunit/xunit/discussions/3163" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/xunit/xunit/discussions/3163</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

xUnit.netWe have just shipped new builds of Core Framework v3, Analyzers, and Visual Studio adapter.Release notes: <a href="https://xunit.net/releases/v3/1.1.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/v3/1.1.0</a> <a href="https://xunit.net/releases/analyzers/1.20.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.20.0</a> <a href="https://xunit.net/releases/visualstudio/3.0.2" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/visualstudio/3.0.2</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

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

sumanthvepaIf you are writing individual unittests, you may be doing testing wrong.I finally <a href="https://mastodon.social/tags/parameterized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#parameterized</a> all the <a href="https://mastodon.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> 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. <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> <a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softwaredevelopment</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a>

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

Brian Okken :python:Goodbye Michael Foord. You will be missed. - Nice write up by Nicholas Tollervey: <a href="https://ntoll.org/article/my-friend-michael/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ntoll.org/article/my-friend-michael/</a> - 2021 interview with him: <a href="https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord</a><a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://fosstodon.org/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> <a href="https://fosstodon.org/tags/mock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mock</a> <a href="https://fosstodon.org/tags/hoopyfrood" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hoopyfrood</a>

sumanthvepa<a href="https://fosstodon.org/@ehmatthes" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ehmatthes</a> No particular reason, other than that <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> comes with the standard library. Maybe, that's all I need to do. Just switch to <a href="https://mastodon.social/tags/pytest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pytest</a>.It is the weekend, and I am writing experimental code. So what the heck. I'll ask ChatGPT to rewrite the tests using pytest.

xUnit.netDo 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.<a href="https://github.com/xunit/xunit/issues/3139#issuecomment-2611568692" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/xunit/xunit/issues/3139#issuecomment-2611568692</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/MicrosoftTestingPlatform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MicrosoftTestingPlatform</a>

xUnit.netUntil now, <a href="https://github.com/xunit/assert.xunit/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/xunit/assert.xunit/</a> has been shared between v2 and v3.Starting today, this repository will become v3 only, and the supported target frameworks and C# language will be updated to be aligned with that.We're adding a v2 branch for people who need to stick there.<a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

xUnit.netWe've created a new documentation page on getting Code Coverage when using Microsoft Testing Platform: <a href="https://xunit.net/docs/getting-started/v3/code-coverage-with-mtp" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/docs/getting-started/v3/code-coverage-with-mtp</a><a href="https://dotnet.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://dotnet.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSharp</a> <a href="https://dotnet.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://dotnet.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

Recent searches

Search options

Administered by:

Server stats:

#unittest