<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Distributed testing frameworks</title>
	<link>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/</link>
	<description>Alex Miller's technical blog</description>
	<pubDate>Thu, 20 Nov 2008 15:39:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Kablooie! &#187; Blog Archive &#187; First Day as Terracotta developer</title>
		<link>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-26507</link>
		<pubDate>Mon, 11 Feb 2008 14:30:01 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-26507</guid>
					<description>[...] As you might expect, this first day was mostly about setting up my computer. Alex and I did talk about what I would work on first, which is the distributed testing framework that is in development and a set of test use cases centered around Terracotta&amp;#8217;s distributed cache functionality.  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As you might expect, this first day was mostly about setting up my computer. Alex and I did talk about what I would work on first, which is the distributed testing framework that is in development and a set of test use cases centered around Terracotta&#8217;s distributed cache functionality.  [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alex Miller - The Grinder 3.0 Released</title>
		<link>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-23218</link>
		<pubDate>Fri, 25 Jan 2008 16:37:02 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-23218</guid>
					<description>[...] I had the occasion recently to evaluate the Grinder for a test system I was building. I was really pleasantly surprised by everything that I found. The Grinder has a fairly clean aesthetic that is hard to quantify but makes getting started a pleasant experience. What I found the most enjoyable about it was the use of Jython to script the actual test activity. Python has a reputation for clean, beautiful code and I found that it was actually fun to hack on the test scripts (once I refreshed my Pythonese a bit). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I had the occasion recently to evaluate the Grinder for a test system I was building. I was really pleasantly surprised by everything that I found. The Grinder has a fairly clean aesthetic that is hard to quantify but makes getting started a pleasant experience. What I found the most enjoyable about it was the use of Jython to script the actual test activity. Python has a reputation for clean, beautiful code and I found that it was actually fun to hack on the test scripts (once I refreshed my Pythonese a bit). [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Travis Swicegood</title>
		<link>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-16606</link>
		<pubDate>Thu, 06 Dec 2007 16:32:13 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/12/05/distributed-testing-frameworks/#comment-16606</guid>
					<description>Hey - Just came across your post via dzone.com.  At my current position I inherited a suite of JMeter test cases and a harness for running and generating reports from its raw data.  I'm now in the process of moving over to The Grinder v3 to take advantage of the ability to script the tests and re-use elements to build larger tests.

JMeter is great for getting a test running quickly, but for long term maintainability, I think the Grinder is an excellent choice between those two.</description>
		<content:encoded><![CDATA[<p>Hey - Just came across your post via dzone.com.  At my current position I inherited a suite of JMeter test cases and a harness for running and generating reports from its raw data.  I&#8217;m now in the process of moving over to The Grinder v3 to take advantage of the ability to script the tests and re-use elements to build larger tests.</p>
<p>JMeter is great for getting a test running quickly, but for long term maintainability, I think the Grinder is an excellent choice between those two.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
