Introducing Laravel Dusk
summary
Laravel Dusk runs real browser tests using the standalone ChromeDriver, exercising a VueJS frontend and Laravel backend together by creating real users, seeding data and asserting UI state; the demo builds a small password app called Fault and the tests run (headless or visible), produce screenshots but no video, and integrate into CI with artifacts. Tests are slow (about a minute for a dozen tests) and require a refreshed non-memory database so database migrations replace transactional tricks.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:05ABOUT ME
- 3:09WHAT IS LARAVEL DUSK?
- 3:55WHAT IS BROWSER TESTING?
- 4:47MANUAL VS AUTOMATED
- 5:56MANUAL BROWSER TESTING
- 7:13AUTOMATED BROWSER TESTING Continous Integration (C)
- 8:20AUTOMATED BROWSER TESTING TOOLS
- 13:22WHEN TO APPLY IT
- 17:05INTRODUCING LARAVEL DUSK
- 18:30HISTORY OF LARAVEL DUSK
- 32:17BENEFITS OF DUSK
- 33:36DISADVANTAGES OF DUSK
