In Typemock we use both NUnit and MSTest to run our unit tests. This practice enables us to check that Isolator works fine on both unit testing framework. Most of NUnit attributes can be translated fully into MSTest attributes (and vise-versa) there is one attribute we tend to use that works differently in MSTest – … Continue reading Checking expected exception message when using MS Test
If you’ve been writing unit tests for some time or seen a good presentation on how to write unit tests you probably heard the “One assert per test” rule. There are real benefits in having only one assert in each tests – you get a focused tests, it’s easier to understand what caused the test … Continue reading Multiple asserts – done right
Test Driven Development (TDD) have many benefits. For start it’s a design methodology that help avoiding “Analysis paralysis” and make sure that you only have the needed code to solve a problem.Yesterday I found another benefit of writing the tests before the code – you get to see them fail!A while back I wrote about … Continue reading Why you need to make your tests fail
In the previous post I’ve explained (briefly) what are fake objects and why they should be used – if you haven’t read it yet – I suggest you do so now. In a nutshell fake objects are used to break dependencies in unit tests to make the test faster, predictable and enable you to test … Continue reading Getting started with Fake Objects – Part 2: How to create a fake object
Helper Code 