home.social

#nunit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nunit, aggregated by home.social.

  1. Monday is perfect day for complaints to be ignored, so here's another one, for NUnit:

    Invalid signature for SetUp or TearDown method: CollectTrampolines

    Thank you very much for doing all those checks and NOT telling me which one of them failed.

    #programming #dotNET #CSharp #NUnit

  2. Testing .NET components that directly use Entity Framework Core can be tricky.

    In this blog post, I show how to glue together libraries like Testcontainers and Respawn with NUnit to create reliable and easy-to-read tests.

    renatogolia.com/2024/08/04/rel

    #dotnet #csharp #efcore #nunit

  3. Put together a sample that shows how to use Appium for your .NET MAUI UI tests!

    This leverages NUnit, Appium and .NET MAUI and lets you run UI tests both on shared code as well as platform-specific functionality.

    learn.microsoft.com/samples/do

    #dotnet #dotnetmaui #uitesting #appium #nunit

  4. 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: jb.gg/ua9vjg

    #dotnet

  5. I noticed that #dotnet 8 is starting to ship #playwright templates for #NUnit and #MSTest. Maybe @xunit should consider a template as well. 🤔

  6. @WadeWegner I've read a lot about (IIRC it's from the same dev that made ). It's a lot simpler to setup, but lacks some features that they feel promotes bad practices. I use NUnit at work with no complaints, but I've been using xUnit for my OSS projects since there's less ceremony (setups are constructors and teardowns are handled by implementing IDisposable)

  7. (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 story here, to celebrate Charlie: github.com/nunit/nunit/discuss

    Thank you, @charliepoole, for all that you've done for NUnit -- and by extension #dotnet developers -- over so much time. You're awesome.

  8. 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: nunit.org/news/update/nunit/20

    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.

  9. The release of #NUNIT v2.0 was on October 3, 2002.

    Allowing developers to unit test their #dotnet applications.

    Do you even unit test? What unit testing framework are you using?

  10. Grateful and excited to announce that I've just become a member of the #NUnit core team! 🎉

    Automated #testing and #TDD have been passions of mine for years, and the opportunity to help steer a #dotnet #oss project with 200+ million downloads is a big one.

    It's a great team and I'm looking forward to continuing to deliver for the community. Now's a wonderful time to get involved; see me if you're interested!

  11. There's more to do! Want to jump in? I'd be happy to guide you through your contribution in our #github repo. Raise your hand to help out here:

    github.com/nunit/docs/issues/4

    We even have a #devcontainer you can use locally or with #codespaces to get started quickly.

    #dotnet #oss #nunit #testing

  12. Latest #OSS fun: the #nunit docs now have a sample project we pull code from for the #docfx docs. Ensures the examples are more reliable, allows us to use our own analyzers & tooling to refactor, lets us check our samples in CI, makes it easier to build out real samples in the future. Very happy about this!

    #dotnet

  13. A fun little bit of #oss hacking tonight! #docfx released a new version that runs as a #dotnet global tool. I was able to update the #nunit docs docfx-action #github action to drastically simplify it. It now is based on the #dotnet #ubuntu container with a small tool install. Then I updated the NUnit docs #devcontainer to be based on that, plus our node tooling.

    Simpler, faster, nicer. Feels good.

  14. Remember in 2002, when you needed this WinForms app to run your #NUnit tests? No... well I do!