Timeline of PHP quality assurance tools

nospam@example.com (Thomas Koch) — Sat, 26 Sep 2009 16:58:46 +0200

I'll be giving a talk on PHP quality assurance tools next week at the gearconf in Düsseldorf. The event is focused on team collaboration and most of the audience will come from other languages then PHP. Since I'm not a contributor to any QA tool I'll center around the user perspective and the process of establishing these tools in a small to middle web company like YMC.
As an outline for the first part I thought to give an historical view on QA in PHP and therefor made a timeline of PHP QA milestones:
The dates as text:

~1997 JUnit
6.4.2002 PHPUnit 0.1
28.8.2003 PHPUnit 1.0.0-alpha1 Release
13.7.2004 PHP5.0.0
14.7.2004 release PHPUnit2
30.1.2006 eZ Components 1.0
~sept 2006 ZF uses PHPUnit (issue #374)
4.10.2006 first integration of Selenium in PHPUnit
1.7.2007 Zend Framework 1.0
18.11.2007 first release of PHPUnderControl
19.11.2007 Project Mess Detection in PHPUnit
6.2.2008 first release PHP_Depend
march 2009 qualityassuranceinphpprojects.com, thePHP.cc

main sources:

Did I get all this right? Are there things I should have added?

PHPUnit Testrunner for Lazy folks

nospam@example.com (Thomas Koch) — Fri, 28 Sep 2007 11:59:33 +0200

My PHPUnit Testrunner must meet the following requirements:

- add Class Repositories to the eZ Components autoloader
- instantiate a Database connection
- make my living easier

I took the testrunner from the eZ Components SVN and added another option for
autoloads that are directly passed to ezcBase::addClassRepository. The instantiation of a db connection is already implemented in the original
code.

Making my living easier works as follows:

I'm to lazy to write a monotonously suite.php for every suite which contains
only the information about the suite name.

Instead of that I put the suite name in the directory:

"tests_search_cars" - Every directory starting with "tests_" is a suite and
the following substring is the suite name. Suites can be nested.

All files ending on "_test.php" are added either to the global test suite or
to the suite represented by the directory they are in.

While working with the tool, I discovered that the ezc testrunner doesn't pass
the filter option to run only tests which match a pattern. This is added in my
runner too.

Some small todos:

- handle wildcards
- add ezc classes and testrunner classes to the filter for code coverage
- support also other locations for autoload files instead of autoload/
- add comments and licence infos...

download: phpunit_testrunner.tar.gz

Thomas Koch - PHPUnit

Timeline of PHP quality assurance tools

PHPUnit Testrunner for Lazy folks