#Need advice: Wait for Pest v4 Fix or Dusk?

4 messages · Page 1 of 1 (latest)

queen terrace
#

tl;dr Should I setup with Dusk or wait for Pest v4 to be fixed?

I'm setting up browser testing for my application and I followed the advice in the Laravel docs to set it up with Pest v4.

That was mostly smooth, until I encountered an issue with testing environments not loading correctly for subdomains - already reported here: https://github.com/pestphp/pest/issues/1520

Now, I could just continue with Dusk, though I'm not sure how difficult it would be to migrate to Pest when that becomes the default for browser testing.

Can anyone offer some advice for what I should do he from a maintainability perspective.

Thanks!

Laravel Dusk - Laravel 12.x - The PHP Framework For Web Artisans

Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.

GitHub
[Bug]: Browser tests for subdomains point to local environment inst...

What Happened We use subdomains as an integral part of our application. E.g. our login route auth.login points to portal.example.test/login. For illustration purposes: Route::domain('portal.exa...

undone mesa
#

Wouldn't Dusk have the same problem though?

queen terrace
# undone mesa Wouldn't Dusk have the same problem though?

Hey thanks for replying. I've used Dusk pipelines which don't seem to run into the same issue. Admittedly it's not been me who's set them up though!

Pest tests hold the environment for other tests, but it when it reaches browser tests it ends up using the default .env environment that's running. I suspect it might not be a trivial fix, though sadly I don't understand the internals enough to judge that.

thorny crypt
#

Pest and dusk can be used together still. If you can’t get pest to do a specific think you can use dusk for that test suite until Pest gets the functionality.