See linked description in GitHub issue.

It is a bit silly that we are running the Chrome extension tests
exclusively in PhantomJS rather than Chrome, but for the moment,
get the existing tests to run using the same getOwnPropertyNames()
shim that is used for the main client app tests.