test coverage

The latest episode of the DevHell podcast has been posted - Episode 3, "Beatings Will Continue Until Test Coverage Improves".

A few weeks ago I wrote an article in which I complained about a few aspects of the PHP development process that I thought were inexcusable and harmful.

The article was surprisingly well-received with only a handful of people responding by demeaning me; given the nature of the article, I'd say that is a big win!

The generally positive response does not make up for the flaws in the article itself, however.

In a (sort of) response to some of the refactoring posts that Brandon Savage has been posting, Dagfinn Reiersol has suggested something that should have been done from the start - write unit tests before you refactor.

There have been a few posts around the community related to the OXID application ever since the Zend Developer Zone posted the latest article in a series looking at using their eShop software.

The quality of the application came up and several even questioned the "94% code coverge" they claimed.

Some of the posts on the matter include:

Jani Hartikainen has posted part five of his look at unit testing in PHP (with PHPUnit) focusing on test-driven development.

Try this: