5 useful tricks for Laravel Dusk

Laravel Dusk is an expressive, easy-to-use, powerful browser automation and testing tool for Laravel. With Dusk you can programmatically test javascript driven applications. Occasionally while writing browser tests with Laravel dusk, I have often run into some limitations. In this article, I will share instances of these situations and how I was able to get past said limitations.

Image for post
Image for post
Source: https://devdojo.com/course/laravel-dusk

1. Filling hidden fields

When testing certain JS components (e.g Autocomplete, Datepickers) It can be strenuous writing actions to simulate DOM clicks/interactions with said components. Since most of these components eventually save the eventual value to a hidden field. It can be more expedient to fill in the hidden field directly with the value. This prevents flaky tests and ensures that we are not testing things we do not own/control (third party components).

While Laravel dusk does not provide us with a method like $browser->fillHidden($field, $value), we can create it ourselves using Dusk Browser Macros

2. Mocking HTML Geolocation

I once had to test a page that needed to provide Geolocation results to the HTML site so it could display some results. There was no direct mock method available so I had to override the getCurrentPosition method which would eventually be called by the page.

3. Using XPath selectors

Occasionally I’d run into situations where I’m unable to use CSS selectors to locate an element. These often happen with dynamic tables or in my case with a third party js component which I couldn’t modify. Laravel Dusk, however, doesn’t support XPath selectors directly and often requires accessing the underlying WebDriver instance.

The only slight [inconsequential] annoyance to this approach is that it might require you to break the fluent method calls on the $browser.

4. Full Page screenshots

Laravel dusks provide us with screenshots of our failed tests and these can be very helpful to know why our tests don’t pass. However, sometimes the error or the element in question might be below the fold.

To create full page screenshots in Laravel Dusk we have to create a captureFailuresFor() method in our tests\DuskTestCase.php which would override the one originally defined in Laravel\Dusk\Concerns\ProvidesBrowser

Now, whenever we call $browser->screenshot('$shotname') or when there’s an error. we’d get a full page screenshot

5. Accessing browser error logs

Ok. This is not a limitation, just something interesting I found. We can access browser console logs by calling $browser->driver->manage()->getLog(‘browser’)

This will return an array of logs in the browser’s console. It can be useful for testing for example that there are no javascript errors on the page.

Be warned though, it doesn’t contain the output of console.log calls


Thanks for reading this, hopefully, you found one or more tip(s) useful.

p.s Please let me know if you notice any errors or inaccuracies in the post and I’d be happy correct it immediately.

Written by

Software Developer. Agnostic. Rebel.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store