Not compatible with PHPUnit 6 about browser-kit-testing

[kamui545]

It's simple.

If you are using PHPUnit 5.x, use browser-kit-testing 1.x
If you are using PHPunit 6.x, use browser-kit-testing 2.x

[phpguru]

For Laravel 5.4, I found that my global PHPUnit > 6 was too new, and just running $ phpunit path/to/test.php was breaking with this error. I had "phpunit/phpunit": "^6.0.3",
in composer.json. After reading this and other similar issues around the web, the problem went away after downgrading PHPUnit by using "phpunit/phpunit": "~5.7", in composer.json, running composer update, and then using the project-specific PHPUnit to run tests $ vendor/bin/phpunit path/to/test.php.

[kamui545]

For some reasons it looks like adding those aliases in config/app.php does not work (at least on my setup)

What I did is adding in tests/BrowserKitTestCase.php the following code (you may need to add more aliases, depending on your tests):

class_alias(\PHPUnit\Framework\TestCase::class, 'PHPUnit_Framework_TestCase');
class_alias(\PHPUnit\Framework\Assert::class, 'PHPUnit_Framework_Assert');
class_alias(\PHPUnit\Framework\Constraint\Constraint::class, 'PHPUnit_Framework_Constraint');

[redgluten]

Ah you’re right, so there’s an issue with the upgrade guide with the command for requiring browser-kit-testing: composer require laravel/browser-kit-testing --dev gets 2.0 despite the guide recommending to use phpunit ~5.7. I’ll submit a PR.

[tms320c]

I use PHPUnit 5.7 and I got laravel/browser-kit-testing version 2.0.0, which does not work with PHPUnit 5
Thanks to @kamui545 it can be fixed in the same but mirrored way: add to tests/BrowserKitTestCase.php the following code:

class_alias('PHPUnit_Framework_TestCase', \PHPUnit\Framework\TestCase::class);
class_alias( 'PHPUnit_Framework_Assert',\PHPUnit\Framework\Assert::class);
class_alias('PHPUnit_Framework_Constraint', \PHPUnit\Framework\Constraint\Constraint::class);

[hohl]

Any ideas why it fails? Would it be hard to fix that and support PHPUnit 6 too? Is it just PHPUnit\Framework\TestCase or would there something else need to change?

[valorin]

A really sneaky cheat for this is to add this into your app.aliases config list:

'PHPUnit_Framework_Assert' => \PHPUnit\Framework\Assert::class,

[redgluten]

Same situation as @tms320c : laravel 5.4.27, browser-kit-testing 2.0.0 and phpunit 5.7.20. I followed the Upgrade guide instructions to keep my existing tests and I got a Fatal error: Class 'PHPUnit\Framework\Constraint\Constraint' not found. Using the class aliases fixed the problem.

Should we open another ticket?

[ajcastro]

What is the recommended browserkit and phpunit to use?

[driesvints]

Library now requires a minimum of PHPUnit 7.0