<?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: Developer testing with the Testivus Manifestivus</title>
	<atom:link href="http://tech.puredanger.com/index.php/2007/02/09/testivus/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.puredanger.com/2007/02/09/testivus/</link>
	<description>Alex Miller&#039;s technical blog</description>
	<lastBuildDate>Mon, 06 Feb 2012 19:39:50 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Rob Breidecker</title>
		<link>http://tech.puredanger.com/2007/02/09/testivus/comment-page-1/#comment-703</link>
		<dc:creator>Rob Breidecker</dc:creator>
		<pubDate>Thu, 15 Feb 2007 15:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://tech.puredanger.com/2007/02/09/testivus/#comment-703</guid>
		<description>Great post Alex.  The &quot;Testivus&quot; post is excellent as well.  Great find.  

I&#039;ve been thinking about what you said in regards to a TDD and if is a good thing or not.  It seems like Web applications might make good candidates for TDD, because the underlying platform and architecture are well know and proven.  Typical Web applications use the MVC design pattern and some combinations of service and data access layers.  All of this is well know and understood by most developers.  In these applications, it is really the business logic and domain model that need to be fleshed out.  So it seems like TDD would work well here.  However, for other applications where the underlying architecture has not been designed, I can see where TDD might not work or lead to poor design.

One more thought.  In a business environment with a large number of Web applications, maybe because of the fact that the platform and architecture are well understood, I am willing to live with less than optimal design, in order to get a large number of tests and a high percentage of code coverage.  I&#039;m not sure I would make that compromise with other less understood, highly complex software.</description>
		<content:encoded><![CDATA[<p>Great post Alex.  The &#8220;Testivus&#8221; post is excellent as well.  Great find.  </p>
<p>I&#8217;ve been thinking about what you said in regards to a TDD and if is a good thing or not.  It seems like Web applications might make good candidates for TDD, because the underlying platform and architecture are well know and proven.  Typical Web applications use the MVC design pattern and some combinations of service and data access layers.  All of this is well know and understood by most developers.  In these applications, it is really the business logic and domain model that need to be fleshed out.  So it seems like TDD would work well here.  However, for other applications where the underlying architecture has not been designed, I can see where TDD might not work or lead to poor design.</p>
<p>One more thought.  In a business environment with a large number of Web applications, maybe because of the fact that the platform and architecture are well understood, I am willing to live with less than optimal design, in order to get a large number of tests and a high percentage of code coverage.  I&#8217;m not sure I would make that compromise with other less understood, highly complex software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alberto Savoia</title>
		<link>http://tech.puredanger.com/2007/02/09/testivus/comment-page-1/#comment-689</link>
		<dc:creator>Alberto Savoia</dc:creator>
		<pubDate>Mon, 12 Feb 2007 00:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://tech.puredanger.com/2007/02/09/testivus/#comment-689</guid>
		<description>&gt;I’ve spent a larger chunk of time than I care to admit &gt;writing testing automation in some form or another. &gt;Even so, I know that every time (and I mean 100%) &gt;I’ve automated something, it paid for itself. Sometimes &gt;it took weeks or months, but it ALWAYS paid for &gt;itself. If you’re on the fence about whether to &gt;automate something (database reset, integration &gt;testing, test scripts, etc), then just do it and trust it’ll &gt;be worth it.

Hi Alex,

I am glad you liked the Testivus idea.  It did start as a sort of joke (could not resist to do something with the &quot;Testivus for the rest of us&quot; phrase), but behind it there&#039;s some serious concern about the fact that most developers are scared off by TDD and some of the other, more dogmatic, movements.

Anyway, the reason I am writing to you is that you really hit the nail on the head when you said that EVERYTIME you&#039;ve automated some tests it was worth your while.  So, with your permission, I&#039;d like to add that concept to the Manifestivus. I tried to capture the idea with testing karma, but your way is more explicit: test automation always pays off.

Thanks and happy coding/testing.

Alberto</description>
		<content:encoded><![CDATA[<p>&gt;I’ve spent a larger chunk of time than I care to admit &gt;writing testing automation in some form or another. &gt;Even so, I know that every time (and I mean 100%) &gt;I’ve automated something, it paid for itself. Sometimes &gt;it took weeks or months, but it ALWAYS paid for &gt;itself. If you’re on the fence about whether to &gt;automate something (database reset, integration &gt;testing, test scripts, etc), then just do it and trust it’ll &gt;be worth it.</p>
<p>Hi Alex,</p>
<p>I am glad you liked the Testivus idea.  It did start as a sort of joke (could not resist to do something with the &#8220;Testivus for the rest of us&#8221; phrase), but behind it there&#8217;s some serious concern about the fact that most developers are scared off by TDD and some of the other, more dogmatic, movements.</p>
<p>Anyway, the reason I am writing to you is that you really hit the nail on the head when you said that EVERYTIME you&#8217;ve automated some tests it was worth your while.  So, with your permission, I&#8217;d like to add that concept to the Manifestivus. I tried to capture the idea with testing karma, but your way is more explicit: test automation always pays off.</p>
<p>Thanks and happy coding/testing.</p>
<p>Alberto</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Sankey</title>
		<link>http://tech.puredanger.com/2007/02/09/testivus/comment-page-1/#comment-677</link>
		<dc:creator>Jason Sankey</dc:creator>
		<pubDate>Sat, 10 Feb 2007 14:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://tech.puredanger.com/2007/02/09/testivus/#comment-677</guid>
		<description>Hi Alex,

Good post.  I feel your frustration at trying to convince devs that tests are a Good Thing.  We are naturally skeptical types and don&#039;t like having things pushed in our faces.  However, if more devs would just try it and get that &quot;feeling&quot; I know they would be infected.

I also like your point about automation paying off.  Every time I finally get around to automating something, I just wish I had done it sooner!</description>
		<content:encoded><![CDATA[<p>Hi Alex,</p>
<p>Good post.  I feel your frustration at trying to convince devs that tests are a Good Thing.  We are naturally skeptical types and don&#8217;t like having things pushed in our faces.  However, if more devs would just try it and get that &#8220;feeling&#8221; I know they would be infected.</p>
<p>I also like your point about automation paying off.  Every time I finally get around to automating something, I just wish I had done it sooner!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

