Re: Blog: Four Ways to test Expected Exceptions
"Brad Stiles" <[email protected]> Sat, 2 Aug 2008 12:57:46 -0400
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <[email protected]> |
Sorry for the cross-posting of the other note. In the referenced blog entry, you mention that you "borrowed" the Assert form of exception checking from xunit.net. Are there any other features of that framework that you plan on borrowing? I checked it out when it was first announced, and there didn't seem to be anything there that would make me want to switch, though if I were newly in the market for a testing framework, it would probably be at or near the top of the list. A good bit of it seems to be about *not* doing some things, and frankly, it's just as easy for me to not do those things in NUnit as it would be to switch to xunit.net and not do them. The one that did jump out at me was the instantiation of a new object for each test. A quick tests reveals that NUnit does not do that, and while I haven't run into any problems so far with side effects, I can see where some sneaky things might slip through. Again, since I haven't had a problem, it's not likely to make me switch, but it does look like a good idea. Brad ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/