News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Greg Beaver's Blog:
Code Coverage Reporting using PEAR, PEAR2, phar, and sqlite3
April 14, 2009 @ 12:08:08

Greg Beaver has a new post reporting on his latest efforts to improve the Pyrus PEAR installer and to make it a more strong, stable and robust end result.

One of the problems I found when designing the new code for PEAR 1.4.0 (back in the day) was that it was very difficult to determine whether changes would break things. The main problem revolves around the colossal size of the test suite. [...] This is a real problem when trying to develop with any kind of flow. If, after every change, one needs to sit through 35 minutes of tests, one will never develop anything of substance.

What he wanted was an application that could detect only the files modified and tests those with the results put into the code coverage report. To fill the need, he created test-modified.php to run just the phpt tests needed.

0 comments voice your opinion now!
codecoverage report phpt unittest pear phar sqlite custom


blog comments powered by Disqus

Similar Posts

Matthias Noback: A better PHP testing experience Part II: Pick your test doubles wisely

Raphael Stolt's Blog: Growling PHPUnit's test status

Kore Nordman\'s Blog: Raytracing with Image_3D

PHPClasses.org: PHP Programming with PEAR

Sara Golemon's Blog: Why isn't this in PEAR?


Community Events





Don't see your event here?
Let us know!


podcast package tips series unittest symfony introduction framework zendserver install api opinion community deployment language library laravel release interview update

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework