<?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>Thu, 20 Jun 2013 03:48:18 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Wim Godden's Blog: Automated PHP 5.3 compatibility testing for your (old) code]]></title>
      <guid>http://www.phpdeveloper.org/news/15616</guid>
      <link>http://www.phpdeveloper.org/news/15616</link>
      <description><![CDATA[<p>
In <a href="http://techblog.wimgodden.be/2010/06/24/automated-php-5-3-compatibility-testing-for-your-old-code/">this new post</a> to his blog today, <i>Wim Godden</i> looks at how you can use the <a href="http://phpunit.de">PHPUnit</a> unit testing framework to be sure your applications are ready to move to a PHP 5.30-only world.
</p>
<blockquote>
So you or your team has built anywhere between 5 and 500 projects in PHP 4, 5.1 and 5.2 over the past 5 years. And now PHP 5.3 is there, offering a lot of very interesting features, including namespace support,  late static binding (finally !), closures, nested exceptions and a bunch more (see the <a href="http://be2.php.net/manual/en/migration53.new-features.php">new feature list</a>). So naturally, you'd like to upgrade. But doing so might break some old code. 
</blockquote>
<p>
He suggests a few different options - just run your unit tests and hope for the best, test the application's code directly or, his preference, run compatibility tests with the help of <a href="http://pear.php.net/package/PHP_CodeSniffer">PHP_CodeSniffer</a> and <a href="http://github.com/wimg/PHP53Compat_CodeSniffer/downloads">this new sniff</a> he created. The sniff finds things like deprecated functions hanging around from pre-5.3 times as a part of a subset that the code sniffer can easily find.
</p>]]></description>
      <pubDate>Wed, 22 Dec 2010 09:02:10 -0600</pubDate>
    </item>
  </channel>
</rss>
