<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: On unit tests in Visual Studio 2008 vs NUnit</title>
	<atom:link href="http://victorsergienko.com/on-unit-tests-in-visual-studio-2008-vs-nunit/feed/" rel="self" type="application/rss+xml" />
	<link>http://victorsergienko.com/on-unit-tests-in-visual-studio-2008-vs-nunit/</link>
	<description>Software design and development: OOD, C++, .NET, Java, a little this and that</description>
	<lastBuildDate>Fri, 25 Jun 2010 13:18:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Victor Sergienko</title>
		<link>http://victorsergienko.com/on-unit-tests-in-visual-studio-2008-vs-nunit/comment-page-1/#comment-829</link>
		<dc:creator>Victor Sergienko</dc:creator>
		<pubDate>Tue, 17 Feb 2009 15:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://victorsergienko.com/?p=44#comment-829</guid>
		<description>That &lt;b&gt;&quot;supported&quot;&lt;/b&gt; is a word people fall under magic of.
Effectively this means that &quot;some issues have a chance to be resolved in the next release in one or two years&quot;.
We had quite a big issues with TFS, and that is what happened.

For NUnit, you have ways greater chance of someone resolving your issue in time, if not yourself.
So, I&#039;d say: &lt;i&gt;(-4) NUnit is opensource and has a good community support.&lt;/i&gt;

For second item, it&#039;s also arguable. To turn VS into a good IDE, I demand ReSharper.
Which supports NUnit ways better then VS does for VS.Test.
Which brings us back to &lt;i&gt;&quot;(-2) GUI that shows where test failed is ugly&quot;&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>That <b>&#8220;supported&#8221;</b> is a word people fall under magic of.<br />
Effectively this means that &#8220;some issues have a chance to be resolved in the next release in one or two years&#8221;.<br />
We had quite a big issues with TFS, and that is what happened.</p>
<p>For NUnit, you have ways greater chance of someone resolving your issue in time, if not yourself.<br />
So, I&#8217;d say: <i>(-4) NUnit is opensource and has a good community support.</i></p>
<p>For second item, it&#8217;s also arguable. To turn VS into a good IDE, I demand ReSharper.<br />
Which supports NUnit ways better then VS does for VS.Test.<br />
Which brings us back to <i>&#8220;(-2) GUI that shows where test failed is ugly&#8221;</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://victorsergienko.com/on-unit-tests-in-visual-studio-2008-vs-nunit/comment-page-1/#comment-828</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 17 Feb 2009 15:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://victorsergienko.com/?p=44#comment-828</guid>
		<description>(+5) it&#039;s supported by microsoft
(+5) they can be run by anyone with VS2008, no external dependencies</description>
		<content:encoded><![CDATA[<p>(+5) it&#8217;s supported by microsoft<br />
(+5) they can be run by anyone with VS2008, no external dependencies</p>
]]></content:encoded>
	</item>
</channel>
</rss>
