101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

506
active users

#unittest

0 posts0 participants0 posts today
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>
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>
xUnit.net<p>We just shipped core framework v3 2.0.1 and source analyzers 1.21.0.</p><p>Check the release notes for new features and bugs fixed.</p><p><a href="https://xunit.net/releases/v3/2.0.1" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/2.0.1</span><span class="invisible"></span></a><br><a href="https://xunit.net/releases/analyzers/1.21.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">.21.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>
Flominator<p>Had an old <a href="https://genealysis.social/tags/unitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unitTest</span></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" target="_blank">#<span>Turkey</span></a> returned by the operating system is meanwhile <a href="https://genealysis.social/tags/T%C3%BCrkiye" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Türkiye</span></a>, which doesn't match the old enum value Turkey anymore.<br><a href="https://genealysis.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://genealysis.social/tags/csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>csharp</span></a></p>
Gary "grim" Kramlich<p>Holy crap! I just noticed we're up to 130 unit test suites in <span class="h-card" translate="no"><a href="https://fosstodon.org/@pidgin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pidgin</span></a></span> 3 now! Compare that to the 7 suites we have in Pidgin 2!</p><p>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!</p><p><a href="https://mastodon.social/tags/Pidgin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pidgin</span></a> <a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</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/Maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Maintainability</span></a> <a href="https://mastodon.social/tags/techdebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>techdebt</span></a></p>
xUnit.net<p>We just shipped core framework v3 2.0.0.</p><p>This contains breaking changes, so the release notes are rather more detailed than normal.</p><p>Release notes: <a href="https://xunit.net/releases/v3/2.0.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/2.0.0</span><span class="invisible"></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>More thoughts about test parallelism as it involves the starting/finished message pairs for test collections, test classes, and test methods.</p><p>If you're a runner author, do you use these messages? Can we just remove them?</p><p>Provide thoughts here: <a href="https://github.com/xunit/xunit/discussions/3164#discussioncomment-12217024" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/xunit/xunit/discuss</span><span class="invisible">ions/3164#discussioncomment-12217024</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/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a></p>
Brad Wilson Taco47<p>Thinking about what an AOT version of <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> would look like. I spent some time talking to <span class="h-card" translate="no"><a href="https://hachyderm.io/@agocke" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>agocke</span></a></span> last year about it so I have some thoughts.</p><p>It almost surely end up being a completely separate code base/package. No mixing and matching, because the internal design would be very different.</p><p>Top three things I think:</p><p>- .NET 8+ only (no .NET Framework)<br>- C# only (no F# or VB)<br>- No extensibility points (you get our Fact and Theory, you get our pipeline).</p><p>1/</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/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://mastodon.social/tags/FSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FSharp</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>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!</p><p><a href="https://github.com/xunit/xunit/discussions/3164" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/xunit/xunit/discuss</span><span class="invisible">ions/3164</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/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a></p>
xUnit.net<p>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?</p><p><a href="https://github.com/xunit/xunit/discussions/3163" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/xunit/xunit/discuss</span><span class="invisible">ions/3163</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/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a></p>
xUnit.net<p>We have just shipped new builds of Core Framework v3, Analyzers, and Visual Studio adapter.</p><p>Release notes:<br><a href="https://xunit.net/releases/v3/1.1.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">xunit.net/releases/v3/1.1.0</span><span class="invisible"></span></a><br><a href="https://xunit.net/releases/analyzers/1.20.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">.20.0</span></a><br><a href="https://xunit.net/releases/visualstudio/3.0.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.0.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 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.</p><p>You may need to add NuGet package references to System.Collections.Immutable and/or System.Memory.</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></p>
sumanthvepa<p>If you are writing individual unittests, you may be doing testing wrong.</p><p>I finally <a href="https://mastodon.social/tags/parameterized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>parameterized</span></a> all the <a href="https://mastodon.social/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> for my deployment tool. </p><p>This is the way testing should be done. </p><p>The way testing is taught, with single unit tests is very misleading.</p><p>With parameterized tests, I can automatically test a significant portion of the input space of function or program. </p><p><a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> <a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwaredevelopment</span></a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a></p>
:rss: DevelopersIO<p>HypothesisでPydanticのPBTをしてみた<br><a href="https://dev.classmethod.jp/articles/hypothesis-pydantic-pbt/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dev.classmethod.jp/articles/hy</span><span class="invisible">pothesis-pydantic-pbt/</span></a></p><p><a href="https://rss-mstdn.studiofreesia.com/tags/dev_classmethod" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dev_classmethod</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/Test" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Test</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pytest</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/%E3%83%86%E3%82%B9%E3%83%88%E8%87%AA%E5%8B%95%E5%8C%96" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>テスト自動化</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/%E3%83%84%E3%83%BC%E3%83%AB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ツール</span></a></p>
xUnit.net<p>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.</p><p>There is no timeline yet for this release.</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></p>
Brian Okken :python:<p>Goodbye Michael Foord. <br>You will be missed. <br>- Nice write up by Nicholas Tollervey: <a href="https://ntoll.org/article/my-friend-michael/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ntoll.org/article/my-friend-mi</span><span class="invisible">chael/</span></a><br>- 2021 interview with him: <a href="https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">testandcode.com/episodes/145-f</span><span class="invisible">or-those-about-to-mock-michael-foord</span></a></p><p><a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://fosstodon.org/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unittest</span></a> <a href="https://fosstodon.org/tags/mock" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mock</span></a> <a href="https://fosstodon.org/tags/hoopyfrood" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hoopyfrood</span></a></p>
xUnit.net<p>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.</p><p><a href="https://github.com/xunit/xunit/issues/3139#issuecomment-2611568692" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/xunit/xunit/issues/</span><span class="invisible">3139#issuecomment-2611568692</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/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://dotnet.social/tags/MicrosoftTestingPlatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MicrosoftTestingPlatform</span></a></p>
:rss: DevelopersIO<p>HypothesisでProperty-Based Testingを始めてみた<br><a href="https://dev.classmethod.jp/articles/pbt-hypothesis-python/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dev.classmethod.jp/articles/pb</span><span class="invisible">t-hypothesis-python/</span></a></p><p><a href="https://rss-mstdn.studiofreesia.com/tags/dev_classmethod" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dev_classmethod</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/Test" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Test</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pytest</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitTest</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/%E3%83%86%E3%82%B9%E3%83%88%E8%87%AA%E5%8B%95%E5%8C%96" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>テスト自動化</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/%E3%83%84%E3%83%BC%E3%83%AB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ツール</span></a></p>
xUnit.net<p>Until now, <a href="https://github.com/xunit/assert.xunit/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/xunit/assert.xunit/</span><span class="invisible"></span></a> has been shared between v2 and v3.</p><p>Starting today, this repository will become v3 only, and the supported target frameworks and C# language will be updated to be aligned with that.</p><p>We're adding a v2 branch for people who need to stick there.</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/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'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" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">xunit.net/docs/getting-started</span><span class="invisible">/v3/code-coverage-with-mtp</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/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>