Sebastian Bergmann has a new post today about a feature of the PHPUnit unit testing tool that has the possibility of breaking when objects are introduced - backing up the globals.

It is hard to test code that uses singletons. The same is true for code that uses global variables. Typically, the code you want to test is coupled strongly with a global variable and you cannot control its creation. An additional problem is the fact that one test's change to a global variable might break another test.

You can disable the backup option if you'd like by setting the $backupGlobals option in your test to false. This lets PHPUnit know that you want to leave the globals (and superglobals) alone during the run.

On the Inside Open Source blog today, there's a "quick hit" post from Jason Gilmore for WordPress users out there using the WP-Cache and being frustrated by it's functionality during the development process.

I'm using WordPress to build out a blog for a new endeavor, and couldn't figure out why I had to go through a rather unwieldy refresh process (disabling a template and then enabling it anew) every time I changed it from within the WordPress administration interface.

It was the WP-Caching mechanism that WordPress comes with that was causing the issue, so he tracked down where to disable it for the duration of the development time. (Options -> WP-Cache -> Disable It).