Tuesday, 27 February 2007
Features and Ideas for PHPUnit Projects |
| |
|
| |
In a new post over at Sebastian Bergmann’s blog, is a list of ideas for features that he would like to see in PHPUnit but currently lacks the time to implement himself. The two ideas are:
- Mutation Testing
- Web Interface for Test Result Database
According to Sebastian, Mutation Testing, or Automated Error Seeding, is an approach where the testing tool makes some change to the tested code, runs the tests, and if the tests pass displays a message saying what it changed. This approach is different than code coverage analysis, because it can find code that is executed by the running of tests but not actually tested. It is not meant as a replacement for code coverage analysis, but complementary.
An implementation of mutation testing for PHP and PHPUnit could use the Parse Tree and Runkit extensions to mutate the tested code, he said.
PHPUnit supports the logging of test result and code coverage data to a database. A web interface, desirably implemented using the eZ Components, is needed to make this data accessible, Sebastian explained.
|
| |
|
|
| |
|
|
| |
|
|
| |
|