code coverage

In July 2010 I already blogged about the fact that HipHop for PHP, the source code transformer that turns PHP code into C++ code that can then be compiled with g++, can also be used for static code analysis to find problems in PHP source code.

Kurt Payne has a new post to his blog showing how you can unit test your process forking in your PHP application (pcntl).

In a new post to his blog Volker Dusch points out a new feature in a recent release of PHPUnit, the popular unit testing framework for PHP - textual code coverage details.

Xdebug's Code Coverage speedup

London, UK Friday, September 23rd 2011, 09:23 BST

Besides a debugging and development aid, Xdebug also implements the back-end code to provide code coverage information for use with PHPUnit.

In my Beyond Frameworks talk, I explained how a component-based architecture can help answe

In my Beyond Frameworks talk, I explained how a component-based architecture can he

Back when I was developing MDB2, I loved my unit tests to help me ensure that changes actually worked across different RDBMS (versions).

It was also a great way to identify issues by having users run the test suite. Actually I guess I wasn't really "unit testing" since I was actually always running against a real database.

Fast forward until today. In my current project we are aiming for 100% code coverage. Well we are not afraid of using @codeCoverageIgnore for super trivial stuff and yes I know that there is more to good tests than just coverage.

Packt: "This article by Daniel Arbuckle, author of Python Testing, introduces code coverage and continuous integration, and teaches how to tie automated testing into version control systems."

On the ZendCasts.com site today there's a new screencast posted showing you how to use Zend_Test to unit test the action helpers in your Zend Framework application.