Where to put browser tests?

[troccoli]

I have been using Cypress for my e2e tests for a while, but I would like to switch to Pest now.

The Pest documentation seems to suggest to have browser tests in tests/Browser, but the pest:test artisan command does not have an option to create browser tests, Pest browser tests that is. It has the --dusk option which indeed creates a test in tests/Browser but it's a Dusk test, so not what I was expecting.

On the other hand, having browser tests in tests/Feature/Browser, which I can create with php artisan pest:test Browser/SignInTest, is handy as I can run all my test with one command.

What do people do? How do you organise your feature and browser tests?

[veljkho]

Pest e2e tests are stored in Browser folder so tests/Browser... and you can call it whatever you like, renaming it to tests/E2E, however, Pest naturally knows it as tests/Browser.. so it will create screenshots in Browser (cannot be changed to e.g. E2E).

Store e2e tests in tests/Browser and that's it. In the tests folder you can have Unit, Feature and Browser tests.. Feature tests are Integration tests, and e2e are Browser tests.

Interesting switch from Cypress. I think Pest Browser still needs to mature to have everything needed. But if you're testing against a Laravel project, then it makes sense.