I recently discovered the constraint model in NUnit. It's been there for years, hiding in plain sight! What is it? Is it worth using? Let's check it out.
Unit testing a WinForms app is an uphill battle in the best of times, before you add in classes like MessageBox. Let's make the best of it.
If you find yourself supporting a WinForms application, you're likely to notice the tests... or lack thereof. Just because we may not have been so focused on automated tests and continuous integration when WinForms was younger, that doesn't mean we can't introduce them now. Better late than never!
When you're writing tests, you generally don't want to write to the database, email customers, and hit third-party API's. That's why we need to know how to mock dependencies!
Porting .NET Framework code to .NET Standard has been a learning experience, with some challenges too. This time I had a .NET Standard library that expected an application config file, but loading one from an NUnit test suite proved to be more difficult than it sounded at first.
I ran into an issue where an EUnit test fixture was failing with an error I hadn't seen before. It seemed to be coming from the meck mocking suite itself, and was reporting that it was 'already_started' and the tests would fail to run... that's a new one. So the obvious question was, WTF@#$ WHY????
While working a code kata last month, I paired with someone to do it in C#. It was a good opportunity for trying out Visual Studio for Mac. Although I've previously kicked the tires on VS4Mac a bit, one of the things I hadn't tried testing out was, well.. testing. As it turns out, it's pretty easy!