Comments on: Automated PHP 5.3 compatibility testing for your (old) code

By: Alberto

Alberto — Wed, 28 Sep 2011 17:25:20 +0000

Hi,

I used your solution in my work and I wrote an script to run this solution in my blog http://blog.albertoviana.com/2011/09/28/how-to-automated-php-5-3-compatibility/ .

By: Resümee des PHP Summit 2011 Spring » Mage::blog()

Resümee des PHP Summit 2011 Spring » Mage::blog() — Wed, 13 Apr 2011 13:36:48 +0000

[...] derUmstellung von PHP 5.2 auf PHP 5.3 lässt sich der Code mit einem Sniff für den PHP_CodeSniffer auf bekannte Problemstellen [...]

By: Tune Up Your PC » Post Topic » This Week’s Link List (December 24, 2010)

Mon, 27 Dec 2010 21:21:57 +0000

[...] Some notes about using PHP_CodeSniffer to upgrade applications to a newer version of PHP: http://techblog.wimgodden.be/2010/06/24/automated-php-5-3-compatibility-testing-for-your-old-code/ [...]

By: Jean-Marc Fontaine

Jean-Marc Fontaine — Wed, 22 Dec 2010 17:26:31 +0000

I have been thinking about doing exactly that for a long time. My idea was not that bad after all.

By: wimg

wimg — Wed, 22 Dec 2010 16:28:03 +0000

If you clone the git repo or download the 1.2 release, it will work for 1.3RC1.
Note the specific instructions about the directory name… I’m looking into changing that part, since it’s a bit annoying…

By: Wim Godden’s Blog: Automated PHP 5.3 compatibility testing for your (old) code | Development Blog With Code Updates : Developercast.com

Wed, 22 Dec 2010 16:16:24 +0000

[...] this new post to his blog today, Wim Godden looks at how you can use the PHPUnit unit testing framework to be [...]

By: Stuardo -StR- Rodríguez

Stuardo -StR- Rodríguez — Wed, 22 Dec 2010 15:49:09 +0000

This means if I clone the latest from the gir repo, it will work for 1.3?

By: wimg

wimg — Mon, 16 Aug 2010 16:44:21 +0000

You’re absolutely right. Because 1.3.0 is still an alpha release, I decided to create the rules for the latest stable release.

I just added the ruleset.xml and refactored the class names so they’re now supported on 1.2.2 and 1.3.0-alpha1.

Thanks for reminding me, cause I completely forgot

By: mike

mike — Wed, 04 Aug 2010 02:20:57 +0000

I was just telling someone people should reuse existing PHP QA tools like PHPCS to detect keywords and other syntax things that may be deprecated in PHP 5.3.

I was excited to see you did most of the footwork. However, it doesn’t work for me. It requires PHPCS version 1.2.2. Not the latest one. The latest one looks for ruleset.xml files inside of each Standards dir.

So here’s the modified instructions:

1) Make sure you are running PHP 5.3!
2) Grab and unpack PHP_CodeSniffer version 1.2.2 from pear.php.net (or pear install it)
3) cd /CodeSniffer/Standards (i.e. cd PHP_CodeSniffer-1.2.2/CodeSniffer/Standards)
4) git clone git://github.com/wimg/PHP53Compat_CodeSniffer.git PHP53Compat
5) run phpcs –standard=PHP53Compat

(the _Sniffer on there messed it up, and the –standard needs to match the directory name, etc.)

By: Wernight

Wernight — Fri, 23 Jul 2010 06:33:37 +0000

I wish this will soon be merged in phpcs core. It’s pretty much a must-have. False-positive are static analysis tools’ killer.

By: Tweets that mention Automated PHP 5.3 compatibility testing for your (old) code « Wim Godden’s professional blog -- Topsy.com

Fri, 25 Jun 2010 00:18:35 +0000

[...] This post was mentioned on Twitter by Greg Sherwood, Wim Godden. Wim Godden said: While waiting for news on #zendcon : new blog post : Automated PHP 5.3 compatibility testing : http://bit.ly/bn9OiQ #php53 #lesstediouswork [...]