compatibility hack for method naming fix from phpunit 3.7.11

[AubreyHewes]

@see https://github.com/Maher4Ever/phpunit-progress/issues/1 @cause https://github.com/sebastianbergmann/phpunit/issues/762

[wadtech]

This request should definitely be accepted. It's a pain to have to edit the file manually after installing the guard-phpunit gem.

[grncdr]

@Maher4Ever just ran into the same thing, please merge.

[erikbrannstrom]

I installed Laravel-Guard which includes guard-phpunit which in turn depends on this library. The problem was that the notification would always say that the tests failed and I should check the console, however that gave no hint of what the problem was.

Anyhow, it turns out to be this issue which wasn't easy to find, so I believe many users of Laravel-Guard and guard-phpunit would be grateful for a merge!

[sgerrand]

@Maher4Ever - Would you be able to review this PR? We have had to fork this repository due to this issue. :crying_cat_face:

[wadtech]

Thanks @AubreyHewes.

@Maher4Ever please accept.

[sgerrand]

@Maher4Ever: I can confirm that this works across multiple PHPUnit versions. Please accept @AubreyHewes' changeset. :wave:

[elliotfleming]

It doesn't seem like @Maher4Ever is going to be fixing this issue... does anyone know what process needs to happen in order to bypass this issue without having to make manual patches every time this gem is installed?

[nifr]

+1 needs to be merged !

[sergigp]

+1 too

[gevans]

:+1: I'd like to see this (or an alternative solution) merged in.