<?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: The Joys of Testing</title>
	<atom:link href="http://theshyam.com/2008/07/the-joys-of-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://theshyam.com/2008/07/the-joys-of-testing/</link>
	<description>Thoughts and factoids from the Real Shyam. You know, unlike those fake ones!!</description>
	<lastBuildDate>Wed, 21 Apr 2010 17:05:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arun Srinivasan</title>
		<link>http://theshyam.com/2008/07/the-joys-of-testing/comment-page-1/#comment-194</link>
		<dc:creator>Arun Srinivasan</dc:creator>
		<pubDate>Sun, 11 Oct 2009 16:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://assertionfailed.wordpress.com/2008/07/12/the-joys-of-testing/#comment-194</guid>
		<description>I still haven&#039;t gotten the difference between asserition programming and contract programming. Any comments?</description>
		<content:encoded><![CDATA[<p>I still haven&#8217;t gotten the difference between asserition programming and contract programming. Any comments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://theshyam.com/2008/07/the-joys-of-testing/comment-page-1/#comment-6</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Tue, 29 Jul 2008 17:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://assertionfailed.wordpress.com/2008/07/12/the-joys-of-testing/#comment-6</guid>
		<description>@akuhn With a stack trace you&#039;ll get your specific line of app code that caused the failure. Or the line at which when tested, the SUT was in an illegal state</description>
		<content:encoded><![CDATA[<p>@akuhn With a stack trace you&#8217;ll get your specific line of app code that caused the failure. Or the line at which when tested, the SUT was in an illegal state</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaurang</title>
		<link>http://theshyam.com/2008/07/the-joys-of-testing/comment-page-1/#comment-5</link>
		<dc:creator>Gaurang</dc:creator>
		<pubDate>Sat, 12 Jul 2008 07:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://assertionfailed.wordpress.com/2008/07/12/the-joys-of-testing/#comment-5</guid>
		<description>SO you do have time....</description>
		<content:encoded><![CDATA[<p>SO you do have time&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: akuhn</title>
		<link>http://theshyam.com/2008/07/the-joys-of-testing/comment-page-1/#comment-4</link>
		<dc:creator>akuhn</dc:creator>
		<pubDate>Sat, 12 Jul 2008 04:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://assertionfailed.wordpress.com/2008/07/12/the-joys-of-testing/#comment-4</guid>
		<description>You wrote:&lt;br/&gt;&gt;&quot;Pin point breakages and causes of failures to the line level&quot;&lt;br/&gt;&lt;br/&gt;Caught my attention. Do you refer to &quot;line of test code&quot; or &quot;line of app code&quot;? If the latter, how do you achieve this? With common unit test, you get the failing line of test code not the failing line of app code. Or even worse, one buggy app line causes dozens or hundreds of test to fail. What is your experience to deal with this?</description>
		<content:encoded><![CDATA[<p>You wrote:<br />>&#8221;Pin point breakages and causes of failures to the line level&#8221;</p>
<p>Caught my attention. Do you refer to &#8220;line of test code&#8221; or &#8220;line of app code&#8221;? If the latter, how do you achieve this? With common unit test, you get the failing line of test code not the failing line of app code. Or even worse, one buggy app line causes dozens or hundreds of test to fail. What is your experience to deal with this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
