<?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: Equals, ==, and MSTest</title>
	<atom:link href="http://hoolihan.net/blog-tim/2010/04/26/equals-and-mstest/feed/" rel="self" type="application/rss+xml" />
	<link>http://hoolihan.net/blog-tim/2010/04/26/equals-and-mstest/</link>
	<description>My Blog</description>
	<lastBuildDate>Mon, 07 May 2012 16:32:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Tim</title>
		<link>http://hoolihan.net/blog-tim/2010/04/26/equals-and-mstest/comment-page-1/#comment-552</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 29 Apr 2010 18:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://hoolihan.net/blog-tim/?p=248#comment-552</guid>
		<description>Sometimes the best way to explain what you want to say about a language is via unit tests.  I could have copied the msdn documentation on == vs Equals, but instead I chose to write two groups of tests that demonstrate the expected results of == or equals depending on the case.

The first group shows what the operators do.  The second case shows how to specify with a unit test where you are testing for reference equality, or some other class defined definition of equality.  

For other examples of this style of documentation, see the ruby koans project (http://github.com/edgecase/ruby_koans) that teaches ruby via unit tests.  If you prefer to communicate about code via long essays of text, by all means head to msdn.com and enjoy.</description>
		<content:encoded><![CDATA[<p>Sometimes the best way to explain what you want to say about a language is via unit tests.  I could have copied the msdn documentation on == vs Equals, but instead I chose to write two groups of tests that demonstrate the expected results of == or equals depending on the case.</p>
<p>The first group shows what the operators do.  The second case shows how to specify with a unit test where you are testing for reference equality, or some other class defined definition of equality.  </p>
<p>For other examples of this style of documentation, see the ruby koans project (<a href="http://github.com/edgecase/ruby_koans" rel="nofollow">http://github.com/edgecase/ruby_koans</a>) that teaches ruby via unit tests.  If you prefer to communicate about code via long essays of text, by all means head to msdn.com and enjoy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duh</title>
		<link>http://hoolihan.net/blog-tim/2010/04/26/equals-and-mstest/comment-page-1/#comment-551</link>
		<dc:creator>Duh</dc:creator>
		<pubDate>Thu, 29 Apr 2010 15:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://hoolihan.net/blog-tim/?p=248#comment-551</guid>
		<description>So what&#039;s your point? Would it have killed you to write a sentence.</description>
		<content:encoded><![CDATA[<p>So what&#8217;s your point? Would it have killed you to write a sentence.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

