<?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: Controlling Testing Environments</title>
	<atom:link href="http://distributedlife.com/blog/2008/04/controlling-testing-environments.html/feed" rel="self" type="application/rss+xml" />
	<link>http://distributedlife.com/blog/2008/04/controlling-testing-environments.html</link>
	<description>passionate about everything</description>
	<lastBuildDate>Tue, 22 Jun 2010 13:04:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chad Stone</title>
		<link>http://distributedlife.com/blog/2008/04/controlling-testing-environments.html/comment-page-1#comment-8</link>
		<dc:creator>Chad Stone</dc:creator>
		<pubDate>Fri, 02 May 2008 09:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://distributedlife.com/blog/2008/04/controlling-testing-environments.html#comment-8</guid>
		<description>That is an excellent point Grant. Automation does rock.&lt;br/&gt;&lt;br/&gt;However, from the perspective of a tester, we don&#039;t usually have a say in whether or not the software deployment process is automated. &lt;br/&gt;&lt;br/&gt;Automating it ourselves, whilst saving time, puts us in the unfortunate situation where deployment no longer matches production.&lt;br/&gt;&lt;br/&gt;So any developers who are reading: Listen to Grant and automate your deployment process. Ideally you should be aiming at the &quot;one-click install&quot; goal.&lt;br/&gt;&lt;br/&gt;And while I&#039;m here, testers: test that the uninstall process leaves the system in a valid state.</description>
		<content:encoded><![CDATA[<p>That is an excellent point Grant. Automation does rock.</p>
<p>However, from the perspective of a tester, we don&#8217;t usually have a say in whether or not the software deployment process is automated. </p>
<p>Automating it ourselves, whilst saving time, puts us in the unfortunate situation where deployment no longer matches production.</p>
<p>So any developers who are reading: Listen to Grant and automate your deployment process. Ideally you should be aiming at the &#8220;one-click install&#8221; goal.</p>
<p>And while I&#8217;m here, testers: test that the uninstall process leaves the system in a valid state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant</title>
		<link>http://distributedlife.com/blog/2008/04/controlling-testing-environments.html/comment-page-1#comment-7</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Fri, 02 May 2008 09:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://distributedlife.com/blog/2008/04/controlling-testing-environments.html#comment-7</guid>
		<description>One of the things that you haven&#039;t mentioned is &quot;automation&quot;.&lt;br/&gt;&lt;br/&gt;I&#039;m a big believer of getting it deployed early - exercise that &quot;deployment muscle&quot;.&lt;br/&gt;&lt;br/&gt;Even if it&#039;s a blank website, or a form with a button on it - spend the time, build your deployment packages, automate where it makes sense, and deploy it through the environments.&lt;br/&gt;&lt;br/&gt;I&#039;ve implemented &quot;manually-initiated automatic deployments&quot; before, and the payoff is amazing.</description>
		<content:encoded><![CDATA[<p>One of the things that you haven&#8217;t mentioned is &#8220;automation&#8221;.</p>
<p>I&#8217;m a big believer of getting it deployed early &#8211; exercise that &#8220;deployment muscle&#8221;.</p>
<p>Even if it&#8217;s a blank website, or a form with a button on it &#8211; spend the time, build your deployment packages, automate where it makes sense, and deploy it through the environments.</p>
<p>I&#8217;ve implemented &#8220;manually-initiated automatic deployments&#8221; before, and the payoff is amazing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

