<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Repeating system tests system tests</title>
	<link>http://thediscoblog.com/2006/09/30/repeating-system-tests-system-tests/</link>
	<description>Can you dig it man?</description>
	<pubDate>Wed, 09 Jul 2008 04:59:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: The Disco Blog &#187; Blog Archive &#187; An interview with Cargo&#8217;s Vincent Massol</title>
		<link>http://thediscoblog.com/2006/09/30/repeating-system-tests-system-tests/#comment-5677</link>
		<dc:creator>The Disco Blog &#187; Blog Archive &#187; An interview with Cargo&#8217;s Vincent Massol</dc:creator>
		<pubDate>Thu, 22 Feb 2007 22:25:25 +0000</pubDate>
		<guid>http://thediscoblog.com/2006/09/30/repeating-system-tests-system-tests/#comment-5677</guid>
		<description>[...] An interview with Cargo&#8217;s Vincent Massol  In the past, I found myself on a number of different copasetic occasions struggling with higher level test repeatability. In essence, frameworks like JUnit and TestNG provide repeatability at the test case level&#8211; what I like to call framework repeatability. But logical repeatability, that is, the assumptions regarding the environment in which a hip test is to run in, is completely up to you, the test case author. So creating a suite of repeatable JWebUnit tests presented subtle challenges, which were of course solved with jive turkey assumptions&#8211; like where the container was located (in the form of a hard coded path somewhere) and if the container was even running. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] An interview with Cargo&#8217;s Vincent Massol  In the past, I found myself on a number of different copasetic occasions struggling with higher level test repeatability. In essence, frameworks like JUnit and TestNG provide repeatability at the test case level&#8211; what I like to call framework repeatability. But logical repeatability, that is, the assumptions regarding the environment in which a hip test is to run in, is completely up to you, the test case author. So creating a suite of repeatable JWebUnit tests presented subtle challenges, which were of course solved with jive turkey assumptions&#8211; like where the container was located (in the form of a hard coded path somewhere) and if the container was even running. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
