<?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"
	>
<channel>
	<title>Comments on: Improving Test Coverage of Ajax Applications</title>
	<atom:link href="http://www.pathf.com/blogs/2006/10/testing_of_ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2006/10/testing_of_ajax/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 21 Nov 2008 11:05:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: John</title>
		<link>http://www.pathf.com/blogs/2006/10/testing_of_ajax/#comment-540</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 05 Apr 2007 17:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=420#comment-540</guid>
		<description>&lt;p&gt;This is interesting. At ArtOfTest, we actually are proposing to segment your application UI into segements called testregions that you inject in your source code. You can then automate against these segments. They offer isolation of these segements from other changes in your application and allow you to be more structured and focused in your testing. Check out TestRegions at www.artoftest.com&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>This is interesting. At ArtOfTest, we actually are proposing to segment your application UI into segements called testregions that you inject in your source code. You can then automate against these segments. They offer isolation of these segements from other changes in your application and allow you to be more structured and focused in your testing. Check out TestRegions at <a href="http://www.artoftest.com" rel="nofollow">http://www.artoftest.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
