Reply to thread

Message

<blockquote data-quote="Chris Tavares" data-source="post: 4139944" data-attributes="member: 10098">NUnit 2.4.7 was just released, so it's under development. Whether you like the direction NUnit has gone in is a very different question.VS unit tests and NUnit tests are pretty much on par feature wise. VS has some nice features for testers (like web tests and setting up database stuff) which are completely useless for, and actually interfere with, developer unit testing.The thing is, VS Unit Tests were designed for testers, not for developers. So it's got tons of stuff about managing and building test lists, storing reports, repeating runs, etc. None of which is anything that's even remotely useful for developer unit tests.The VS test runner is a little better in 2008, but it's still awkward. If you want a really good unit testing experience, go download from <a href="http://www.testdriven.net/" target="_blank">http://www.testdriven.net/</a> . It's a VS addin that lets you right click on a test class or method, or on anything in the solution explorer, and it'll go out and run the tests. It's the simplest thing that could possibly work, and it works fantastically well.As for the observer discussion, put me down on the &quot;overkill&quot; side. I'm a big fan of the YAGNI principle: You Ain't Gonna Need It. I've had lots of projects in the past where I've put in generality that &quot;I know I'm going to need!&quot; but ended up not needing at all. The result being carrying around lots of maintenance burden for overly general stuff that wasn't even being used.Yeah, I'm one of those agile hippy freaks I guess. ;-)</blockquote>

[QUOTE="Chris Tavares, post: 4139944, member: 10098"] NUnit 2.4.7 was just released, so it's under development. Whether you like the direction NUnit has gone in is a very different question. VS unit tests and NUnit tests are pretty much on par feature wise. VS has some nice features for testers (like web tests and setting up database stuff) which are completely useless for, and actually interfere with, developer unit testing. The thing is, VS Unit Tests were designed for testers, not for developers. So it's got tons of stuff about managing and building test lists, storing reports, repeating runs, etc. None of which is anything that's even remotely useful for developer unit tests. The VS test runner is a little better in 2008, but it's still awkward. If you want a really good unit testing experience, go download from [url]http://www.testdriven.net/[/url] . It's a VS addin that lets you right click on a test class or method, or on anything in the solution explorer, and it'll go out and run the tests. It's the simplest thing that could possibly work, and it works fantastically well. As for the observer discussion, put me down on the "overkill" side. I'm a big fan of the YAGNI principle: You Ain't Gonna Need It. I've had lots of projects in the past where I've put in generality that "I know I'm going to need!" but ended up not needing at all. The result being carrying around lots of maintenance burden for overly general stuff that wasn't even being used. Yeah, I'm one of those agile hippy freaks I guess. ;-) [/QUOTE]

Verification