Ideas

Here are some ideas for features that  Sebastian Bergmann would like to see in PHPUnit but currently lacks the time to implement. If you are interested in working on these ideas feel free to get in touch.

Gearman-based Implementation for Process Isolation

PHPUnit_Util_PHP::runJob() (PHPUnit/Util/PHP.php) currently takes a job in the form of a PHP script that is executed in a fresh/separate PHP process on the same machine. A  Gearman-based implementation of process isolation would hand this job off to a worker that might be on a different machine.

Integrated Coverage of C and PHP Code

It might be worthwhile to implement a parser for gcov data files ( #1,  #2) in PHP to integrate the code coverage information for PHP and PHP extensions into PHPUnit's code coverage report. This could be helpful for developers that write both C-level and PHP-level code for their PHP applications.

Automated SimpleTest to PHPUnit Conversion

A request that I keep getting is that for a script that automatically converts test written for  SimpleTest into tests for PHPUnit.

Automated Whitebox Test Generation

Using a combination of static analysis and runtime analysis (like  php-tracer-weaver, for instance), a tool could look for interesting input-output values of your methods and automatically generate a set of tests based on boundary conditions, exceptions, etc.

Automated Characterization Test Generation

 Characterization Tests do not check what the code is supposed to do, as specification tests do, but what the code actually and currently does ( Alberto Savoia).

 JUnit Factory, for example, is a characterization test generator for Java and JUnit.

Model-Based Testing

Port  ModelJUnit to faciliate  Model-Based Testing.