Neat! #Duende is sponsoring #dotnet project Shouldy for the next year for $3,000. #unittesting #xunit #nunit #mstest
https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/
Microsoft.Testing.Platform: Now Supported by All Major .NET Test Frameworks.
https://devblogs.microsoft.com/dotnet/mtp-adoption-frameworks/?hide_banner=true
#mstest #xunit #nunit #dotnet #unittesting #csharp
Microsoft.Testing.Platform: No...
With #testcontainers, you can spin up and tear down #Docker containers in your tests.
If you need a database, you don’t need to mock it: your #xUnit, #NUnit, and #MSTest code can launch an actual database!
Learn more in this blog post by @khalidabuhakmeh: https://jb.gg/ua9vjg
(And those are only the ones we can easily find; our numbers are sourced from after NUnit moved the project to #GitHub in 2011, which means there are *at least 9 additional years of work* not quantified above.)
Has #NUnit helped you, your career, or your organization? We'd love for you to tell that store here, to celebrate Charlie: https://github.com/nunit/nunit/discussions/4283
Thank you, @charliepoole, for all that you've done for NUnit -- and by extension #dotnet developers -- over so much time. You're awesome.
Few #dotnet #oss projects have the longevity of #NUnit. After *over 20 years* of stewarding the project, @charliepoole is stepping back.
Read our announcement / appreciation here: https://nunit.org/news/update/nunit/2023/01/29/celebrating-charlie-poole.html
To attempt to quantify Charlie’s contributions to NUnit is a daunting task. He was the lead of NUnit across at least 207 releases in 37 different repositories, authoring 4,898 commits across them. He participated in 2,990 issues, 1,305 PRs, and impacted 6,992,983 lines of code.
Remember in 2002, when you needed this WinForms app to run your #NUnit tests? No... well I do!
