<?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: Tips for Testing Plugins</title>
	<atom:link href="http://www.pathf.com/blogs/2008/09/tips-for-testing-plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/09/tips-for-testing-plugins/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 09 Jan 2009 09:45:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Aaron Pfeifer</title>
		<link>http://www.pathf.com/blogs/2008/09/tips-for-testing-plugins/#comment-3367</link>
		<dc:creator>Aaron Pfeifer</dc:creator>
		<pubDate>Sat, 13 Sep 2008 03:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1146#comment-3367</guid>
		<description>Great writeup... definitely covers the basics for plugin testing.  However, I would *highly* recommend taking a look at the plugin_test_helper library (http://github.com/pluginaweek/plugin_test_helper).  This encapsulates the entire environment setup process and has made it really easy to test plugins in isolation.  Most of the plugins in the pluginaweek project use this library for setting up test environments.</description>
		<content:encoded><![CDATA[<p>Great writeup&#8230; definitely covers the basics for plugin testing.  However, I would *highly* recommend taking a look at the plugin_test_helper library (http://github.com/pluginaweek/plugin_test_helper).  This encapsulates the entire environment setup process and has made it really easy to test plugins in isolation.  Most of the plugins in the pluginaweek project use this library for setting up test environments.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
