<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Mon, 20 May 2013 04:14:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Volker Dusch's Blog: Running your Unittests everytime you save a file]]></title>
      <guid>http://www.phpdeveloper.org/news/15626</guid>
      <link>http://www.phpdeveloper.org/news/15626</link>
      <description><![CDATA[<p>
<i>Volker Dusch</i> has a suggestion for all of those developers out there really concerned about the quality of your code - consider running your unit tests every time you save a file with the help of a tool called <a href="http://heisel.org/blog/code/pywatch/">PyWatch</a>.
</p>
<blockquote>
At the moment he placed the Idea in my head that i want my testsuite to run every time a file changes anyway, let someone else figure out how that is triggered. Well, <a href="http://heisel.org/blog/code/pywatch/">someone did figure that out, thank you</a>. It's called "PyWatch" and is a simple python script that monitors files for changes and executes a script if one has changed.
</blockquote>
<p>
Obviously you wouldn't want to keep this going for larger code bases (the potential for overlap is horrible) but it could be quite useful when doing test-driven development to save yourself some hassle at the outset. He includes the commands you'll need to get things running and a simple PHP script that points the PyWatch instance to the correct files.
</p>]]></description>
      <pubDate>Thu, 23 Dec 2010 11:55:23 -0600</pubDate>
    </item>
  </channel>
</rss>
