<?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: Tips for Testing Plugins</title>
	<atom:link href="http://pathfindersoftware.com/2008/09/tips-for-testing-plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathfindersoftware.com/2008/09/tips-for-testing-plugins/</link>
	<description>The Fastest Way to Launch Successful Software</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Bill</title>
		<link>http://pathfindersoftware.com/2008/09/tips-for-testing-plugins/#comment-8661</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Fri, 01 May 2009 00:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1146#comment-8661</guid>
		<description>AHHG!  This is the 10th tutorial I&#039;ve Googled that has told me how to SETUP the tests for my Rails plugin, and the 10th that has not told me how to run the damn things (I know, rake test:plugins to run tests for all plugins, but what about for one?)!

Sorry.  Not your fault any more than the other 10.  But this seems like a pretty obvious need that Google is woefully underprepared for.</description>
		<content:encoded><![CDATA[<p>AHHG!  This is the 10th tutorial I&#8217;ve Googled that has told me how to SETUP the tests for my Rails plugin, and the 10th that has not told me how to run the damn things (I know, rake test:plugins to run tests for all plugins, but what about for one?)!</p>
<p>Sorry.  Not your fault any more than the other 10.  But this seems like a pretty obvious need that Google is woefully underprepared for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Pfeifer</title>
		<link>http://pathfindersoftware.com/2008/09/tips-for-testing-plugins/#comment-8660</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-8660</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 (<a href="http://github.com/pluginaweek/plugin_test_helper" rel="nofollow">http://github.com/pluginaweek/plugin_test_helper</a>).  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>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (User agent is rejected)
Page Caching using memcached (User agent is rejected)

Served from: pathfindersoftware.com @ 2012-02-10 00:55:34 -->
