FIX: Update SapphireTest to match phpunit 4

[sminnee]

This appears to be the only change necessary to get the tests building on phpunit 4. We'll see if the pull requests fails build on another phpunit...

[simonwelsh]

This breaks Behat, since it'll need to pull in PHPUnit 4 as well.

[chillu]

I think this is blocked until we upgrade to Behat 3.0. The Behat version we're currently relying on (2.5) is setting "phpunit/phpunit": "~3.7.19" (https://github.com/Behat/Behat/blob/2.5/composer.json#L29). And updating Behat is a larger effort (days rather than hours I think). @jeffreyguo has made a start on this update I think.

[tractorcow]

Good spot @chillu. I knew it wouldn't be a trivial task.

[tractorcow]

@chillu Should we perhaps aim for 3.2 for behat 3 / phpunit 4 support?

[chillu]

Behat 3 upgrade progress is tracked here, its a PITA: silverstripe/silverstripe-behat-extension#62. Aiming for 3.2 sounds reasonable though

[simonwelsh]

This can be pulled safely just without the composer change. I suggest that @sminnee removes that change, then this can be merged so that PHPUnit 4 can be used with E_STRICT enabled (the HHVM framework tests use PHPUnit 4, though seem to have E_STRICT off).

[chillu]

This has been fixed through 19e0d5e already (without pulling in the composer change)