Laravel Dusk simplifies browser automation testing, running directly with ChromeDriver without Selenium or JDK. 1. Install: composer requires --dev laravel/dusk, and then run php artisan dusk:install. 2. Create a test: php artisan dusk:make LoginTest, use visit(), type(), press(), and assertPathis() to simulate user operations in the test. 3. Common methods include click(), check(), select(), attach(), waitFor(), assertSee(), etc. 4. Run the test: php artisan dusk. If it fails, you can debug through screenshot() and console logs. 5. Configure .env.dusk.local to set up an independent test environment. 6. Best practices: Use page-based organization logic, single-test single scenarios, use waitFor() to reduce fluctuations, and run in headless mode in CI/CD. Finally, the test is executed through php artisan dusk and the result is generated.

Laravel Dusk is a powerful tool for running browser automation and testing, making it easy to interact with your application just like a real user would—clicking buttons, filling forms, navigating pages, and asserting content. It uses ChromeDriver by default and doesn't require JDK or Selenium, which makes setup simpler than older tools.

Here's how to get started and use Laravel Dusk effectively.

? Install and Set Up Laravel Dusk

First, install Dusk via Composer:

 composer requires --dev laravel/dusk

Then register the service provider (in Laravel 10 and earlier, this may be needed):

 php artisan dusk:install

This creates a tests/Browser directory and a sample test.

Note: In Laravel 11 , Dusk may be included by default, and the structure is slightly different.

? Write Your First Browser Test

Generate a new browser test:

 php artisan dusk:make LoginTest

This creates tests/Browser/LoginTest.php .

Edit it to test a login flow:

 <?php

namespace Tests\Browser;

use Laravel\Dusk\Browser;
use Tests\DuskTestCase;

class LoginTest extends DuskTestCase
{
    public function testBasicExample()
    {
        $this->browse(function (Browser $browser) {
            $browser->visit(&#39;/login&#39;)
                    ->type(&#39;email&#39;, &#39;user@example.com&#39;)
                    ->type(&#39;password&#39;, &#39;password&#39;)
                    ->press(&#39;Login&#39;)
                    ->assertPathIs(&#39;/dashboard&#39;);
        });
    }
}

In this example:

• visit() goes to the login page.
• type() fills in input fields by name or selector.
• press() clicks a button with matching text.
• assertPathIs() checks the URL after login.

? Useful Dusk Browser Methods

Here are common methods you'll use:

• visit('/url') – Navigate to a page.
• click('selector') – Click an element.
• type('field', 'value') – Fill input fields.
• check('checkbox') / uncheck() – Handle checkboxes.
• select('dropdown', 'option') – Choose from a select.
• attach('file_input', '/path/to/file.jpg') – Upload a file.
• waitFor('.selector') – Wait for an element to appear.
• assertSee('text') – Assert text is on the page.
• assertVisible('.selector') – Assert element is visible.
• assertPathIs('/expected/path') – Confirm current URL.

You can also use CSS selectors or Dusk's magic short syntax:

 $browser->type('#email', 'test@example.com'); // CSS selector
$browser->check('terms'); // by name

?? Run the Tests

Make sure Chrome is installed. Then run:

 php artisan dusk

Dusk will:

• Launch Chrome (via ChromeDriver).
• Run your tests.
• Output results in the terminal.

If you get errors about ChromeDriver version, update it:

 php artisan dusk:chrome-driver

You can also specify a version:

 php artisan dusk:chrome-driver 125

? Testing in Different Environments

By default, Dusk runs on http://127.0.0.1:8000 . You can change the base URL by setting APP_URL in your .env.dusk.local file:

 APP_URL=http://myapp.test

Dusk automatically uses .env.dusk.local during testing, so your database or other settings won't be affected.

Create .env.dusk.local and keep it out of version control.

? Debugging with Screenshots and Console Logs

If a test fails, Dusk can take a screenshot and record console logs.

Enable it in your test class:

 protected function failed($method)
{
    $this->browse(function ($browser) use ($method) {
        $browser->storeScreenshot($method);
        $browser->script('return console.logs');
    });
    parent::failed($method);
}

Or manually take a screenshot:

 $browser->screenshot('login_error');

Screenshots are saved in tests/Browser/screenshots .

? Best Practices

• Use page classes for complex apps. Group common actions (like login, navigation):

   php artisan dusk:page Login

• Keep tests focused: one test per scenario.

• Avoid flaky tests by using waitFor() before interacting with dynamic content.

• Run Dusk in CI/CD using headless Chrome (set via environment or Dusk options).

---

Basically, Laravel Dusk simplifies browser testing by giving you an expressive API to simulate real user behavior—no Selenium setup needed. Just write tests, run php artisan dusk , and let Chrome do the rest.

The above is the detailed content of How to use Laravel Dusk for browser testing?. For more information, please follow other related articles on the PHP Chinese website!