Switching to Pest for hypervel/hypervel

[binaryfire]

Hey @albertcht. I noticed the docs say Pest isn't supported but I just tested it in the skeleton and it seems to be working fine. The use of TestCase In Pest.php is commented out by default - could that have been the problem last time you tried it? To double check, I changed the phpunit.xml cache driver to redis, added a few cache tests and ran with --parallel. Everything passed.

It's only pulling in Pest v2 because hyperf/testing still uses PHPUnit v10, but it still aligns better with Laravel's skeleton. I think keeping things as familar as possible for Laravel devs is important. They'll definitely want to use Pest. Shall I make a PR to change it in the skeleton?

[albertcht]

Hi @binaryfire , I originally planed to migrate https://github.com/pestphp/pest-plugin-laravel for full support like in Laravel. And I haven't made a full test for that. Welcome for any PRs about the pest integration.

[binaryfire]

@albertcht I'm closing this because I've recently moved away from Pest back to PHPUnit. Pest is quite opinionated, which can make it hard to extend. For example uses() and extends() is a lot less flexible for custom setups than than just using classes. Personally, my vote is to stick with PHPUnit.