This post originated from an RSS feed registered with PHP Buzz
by Sebastian Bergmann.
Original Post: Profiling and Optimizing PHPUnit
Feed Title: Sebastian Bergmann on PHP
Feed URL: http://sebastian-bergmann.de/rss.php?category=6&version=2.0
Feed Description: Sebastian Bergmann is a long-time contributor to various PHP projects, including PHP itself. He is currently working for eZ Systems AS on the Workflow Engine component for the eZ Platform. As the developer of PHPUnit, he also helps with testing the eZ Components. In his free time he likes to hack on Open Source software and to take photographs, preferably while travelling the world.
Now that collecting code coverage information is not slow anymore (as of Xdebug 2.0.1 ), PHPUnit's report generation code ( PHPUnit_Util_Report_* ) has become a bottleneck.
The image above shows the profile of PHPUnit 's report generation code at revision 1473 .
The image above shows the profile of PHPUnit 's report generation code at revision 1475 , after I made the report a code coverage report only.
The test result aspect of the previous report was not very usefull, made the report generation unneccassary complex and expensive, and should be handled by CruiseControl , for instance, anyways.
Previous Topic
