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?

@khalidabuhakmeh xUnit mostly, sometimes MSTests.

I am doing more and more TDD.

@khalidabuhakmeh The only time I unittested in my life was in Swift, with XCtest, becuase i could never grasp concepts of Unit Testing

@khalidabuhakmeh I really dislike nunit. It makes it too easy to focus on doing things that lead to bad tests.

The SetUp methods lead to hidden context. It's fine sometimes, but too many people use it for all code they want in every test. It's always a point of problems in suites that use nunit.

Not that xunit handles fixtures/context perfectly, but at least it makes you put in a bit of work to point the gun at your foot.

@jakecarpenter @khalidabuhakmeh

Interesting. I was interested in the differences between the two recently. Can you describe more, or do you have any links about it?

@mikehe

They touch on the topic in the xunit documentation and in linked blog posts: https://xunit.net/docs/why-did-we-build-xunit-1.0

I'm sure a bit of googling around "shared unit test setup" would yield a lot of opinions similar to mine as well.

Why Did We Build xUnit 1.0?

Documentation site for the xUnit.net unit testing framework

xUnit.net
@khalidabuhakmeh I'm still using NUnit, in fact, I've been trying to write tests today that mock repositories and mediatr, it's a learning curve for me, ive only really got into UTs in the last 4 or 5 years
@cer awesome. Good luck and be sure to write a blog post about it. Would love to read about what you end up on.
@khalidabuhakmeh
Oh yes, saved me too many times not too. Mostly use NUnit. Dabbled in xUnit.
@khalidabuhakmeh nunit because i despise xunit's unintuitive names like fact, theory, etc.
@ssg Yeah, I feel NUnit is much better at naming, while xUnit seems somewhat better at behavior (F# async support out of the box, plain constructors and `Dispose` instead of all the nasty `[SetUp]` stuff).
@fornever i agree, many good ideas in xUnit. shame that they had to be stuck-up about naming.
@khalidabuhakmeh A wise man once said: "If you aren't testing your code, it isn't working!"
@fornever I can send you an exe that hasn't been tested. It definitely works. I swear it does.
@khalidabuhakmeh Hey, tell that to the wise man, not me!
@khalidabuhakmeh I used to use either Nunit or Xunit. Been a few months since I've done serious dotnet though - sadfacedotgif
@paulnewman what are you doing?
@khalidabuhakmeh I've moved into a broader technical principal role at a professional services place - so now I get to look at lots of other tech - like Java, AWS, and whatnot. On macs. qhich is a learning experience. I still miss just flat out all day dotnet though 😁
@paulnewman sounds really cool
@khalidabuhakmeh It's a change from app development! Basically the tech stack is going to end up being: whatever the customer has. I had to install IntelliJ the other day 😁
@khalidabuhakmeh I started with NUnit and I still use NUnit. 💪
@khalidabuhakmeh I can't lie, one of my current clients is still on NUnit v2
@khalidabuhakmeh since xUnit is right there in the 'dotnet new' templates, I just use that lol.
@aristurlte but so is NUnit :)
@khalidabuhakmeh Oh wow, so it is lol. I never noticed it since xUnit shows up as the last item in 'dotnet new'.