Conversation
|
ℹ️ Pest Browser Testing is built on top of Playwright. While Shift added this as an NPM dependency, you will need to run |
|
|
|
ℹ️ To run your browser tests, Dusk required you to run an instance of your application in the background. With Pest Browser Testing, your tests run your application directly. This allows you to leverage the full power of Laravel's testing layer, such as refreshing the database and built-in faking. It also allows you to more easily run your browser tests. Often you may simply run |
|
ℹ️ Since Dusk ran separately from your application, your Dusk tests did not use the common testing traits for managing services. For example, the Your Pest Browser tests will likely need to use these traits. You may quickly configure all your browser tests to use them within your pest()->extend(TestCase::class)->use(RefreshDatabase::class)->in('Browser'); |
|
⚗️ This Shift is still being refined. Please report any issues or suggestions to shift@laravelshift.com. Your feedback is what helps improve the experience for everyone. |
This pull request includes the changes for converting your Laravel Dusk tests to Pest Browser Tests. Feel free to commit any additional changes to the
shift-163241branch.Before merging, you need to:
shift-163241branchcomposer update(if the scripts fail, try with--no-scripts)npm updatephp artisan testIf you get stuck, never hesitate to email support. If you need more help with your upgrade, check out the Human Shifts.