New ExpectedException model in NUnit 2.5
A new version of NUnit is released and there is a new way to handle expected exceptions. Until recently NUnit did this by putting an attribute on your test method, very much how MsTest still works.
/* Test */ numberOfNames = names.Length;
You read by the method header that this test is throwing an exception. The test runner will catch the specified exception and try to determine if it was the expected exception thrown. The bad thing about this is that you put your assertion outside your test and that hurts readability. The NUnit team has conjured up the following solution.
/* Assert */ Assert.Throws<NullReferenceException>( /* Test */ () => numberOfNames = names.Length); /* Assert that numberOfNames is still zero */ Assert.That(numberOfNames == 0);
The assert is nicely put inside the test and you can actually assert that there were now side effects from the thrown exception. This is a major improvement. What bothers me is that it looks like my first assertion comes before the test. We all know that the test has to run first, because it is an argument that has to be evaluated, but this does not really look good either.
/* Test */ TestDelegate throwingCode = () => numberOfNames = names.Length; /* Assert */ Assert.Throws<NullReferenceException>(throwingCode); /* Assert that numberOfNames is still zero */ Assert.That(numberOfNames == 0);
Pretty neat, huh! Keep it up, NUnit team! You know that we all love you.