News Feed
Sections




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

Sebastian Bergmann's Blog:
CRAP in PHPUnit 3.5
January 12, 2010 @ 11:14:03

As Sebastian Bergmann mentions in his latest post, he's changed up how the code coverage functionality is handled in PHPUnit so that he can add something new - CRAP.

PHP_CodeCoverage is a component that provides collection, processing, and rendering functionality for PHP code coverage information. [...] Having all code that deals with code coverage in a separate component allows for easier development and better testing. The first result of these improved development conditions is a small new feature that I recently implemented, the support for the CRAP metric.

Your code's CRAP (Change Risk Analysis and Predictions) scoring combines the idea of cyclomatic complexity and code coverage statistics to try to guess at how difficult any given piece of code would be to maintain. You can see an example here - the lower the number the better.

0 comments voice your opinion now!
crap cyclomatic complexity codecoverage phpunit unittest


blog comments powered by Disqus

Similar Posts

Mike Lively's Blog: PHPDBUnit - Testing DB interaction with PHPUnit

Ryan Mauger's Blog: Controller Testing with the FlashMessenger in Zend Framework

Tom Oram's Blog: Unit testing a Zend Framework 2 Controller

Change Garcia's Blog: expected exceptions annotations, mocked object calls, oh my.

Test.ical.ly Blog: Best practice of PHPUnit testing a symfony 1.4 plugin


Community Events





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


laravel framework threedevsandamaybe opinion introduction community developer unittest language api interview series podcast install refactor code testing list release symfony2

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