Stefan Priebsch has posted an example of how he uses PHPUnit "manually" to reduce the overhead (and added complexity) of calling phing.

Instead of instantiating PHPUnit from phing, I use the command line interface to call PHPUnit. This decouples phing and PHPUnit, which should cause less problems with version updates in the future. To configure PHPUnit, phing creates a temporary XML configuration file which is deleted after PHPUnit has finished.

The source is included in the post - it manually builds the XML file needed for phing to do its job.

Elizabeth Smith has posted about a new toy she received from the folks at Microsoft that adds in a missing piece of development functionality on Windows - code coverage and testing.

So this evening I managed to get PHPT running my tests (they're just basic .phpt tests but run-tests is..well flakey is a nice description some days) for my winapi php extension wrapped inside a "generic test" for Visual Studio. [...] So what did all this accomplish? I now can run my phpt tests through visual studio and collect code coverage on what they’re testing. Like GCOV, only for windows.

She's also included a screenshot of what the interface and results of the testing look like in the latest Visual Studio tool.