mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

376K
active users

#nunit

0 posts0 participants0 posts today

I'm at a loss here. I was testing out if upgrading NUnit in our test automation code repo from 3.x to 4.x would be a neat idea. So I did the upgrade, made the proper modifications to the now-outdated asserts, ran the tests...

And they're all inconclusive?

They are correctly pass/fail/whatever when using 3.x but with 4.x the TestContext shows every single test as inconclusive in TearDown, where I take the result and log it to console. And after TearDown, it apparently remains inconclusive, since the reporting tool also showns it as such.

I don't know where else to go with this so I'll just scream in to the void in the hopes that someone might have even a slight idea where I should start looking into this issue. I tried scouring the breaking changes and whatnot, but nothing seems to obviously hint towards why the TearDown no longer has the correct TestContext (or why the TestContext is screwed after Assert). Otherwise I guess I'm just gonna skip the entire 4.x and stay at 3.x until the sun explodes.

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

learn.microsoft.com.NET MAUI - UI testing with Appium and NUnit - Code SamplesSample solution that demonstrates how to setup your .NET MAUI app for UI testing with Appium and NUnit.
Replied in thread

@WadeWegner I've read a lot about #xunit (IIRC it's from the same dev that made #NUnit ). 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)

Continued thread

(And those are only the ones we can easily find; our numbers are sourced from after NUnit moved the project to in 2011, which means there are *at least 9 additional years of work* not quantified above.)

Has 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 developers -- over so much time. You're awesome.

GitHubCelebrating Charlie: How has NUnit helped you, your career, or your organization? · Discussion #4283 · nunit/nunitWe're celebrating the incredible commitment Charlie Poole has made to the NUnit community in his 20+ years of stewarding the NUnit project. As part of that, we'd love to hear -- how has NUn...

Few projects have the longevity of . 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.

nunit.orgCommemorating Charlie Poole's Contributions to the NUnit ProjectNUnit has been around for a while – it debuted in 2000, along with .NET itself. And while he didn’t originate the project, for over 20 years now NUnit has be...

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

Automated and have been passions of mine for years, and the opportunity to help steer a 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!