konsulting/dusk-standalone

Standalone dusk testing, ideal for legacy projects, or remote testing.

Dusk Standalone

A simple package to use Laravel Dusk with PHPUnit outside of a Laravel application for browser testing., _(*1)

The package was put together to allow local and remote testing of legacy applications which do not have similar testing frameworks available. There are other options for doing so, but we like the API for Dusk., _(*2)

Perhaps not everything will work as expected, since we're not integrated to Laravel. It's early days for this package, so it's open to improvement., _(*3)

We also assist with another package, designed for using Laravel Dusk to test Laravel Packages, Orchestra Testbench-Dusk., _(*4)

, _(*5)

Version Compatibility

The versioning for this package aligns with major releases of Dusk., _(*6)

Installation

We recommend using composer., _(*7)

composer require konsulting/dusk-standalone, _(*8)

Usage

We tend to put our Browser tests in tests/Browser. Create a new base testcase that extends the Konsulting\DuskStandalone\TestCase., _(*9)

This will allow you to add any customisations you want in your Dusk tests., _(*10)

<?php

namespace Application\Tests;

use Konsulting\DuskStandalone\TestCase;

abstract class DuskTestCase extends TestCase
{
    // Set the base url for the browser requests
    protected function baseUrl()
    {
        return 'https://www.klever.co.uk';
    }

    // Set the path for browser tests, this is where screenshots/console logs
    // are stored. The default is [app root]/tests/Browser based on the 
    // vendor folder location as per a normal Composer install.
    protected function browserTestsPath()
    {
        return parent::browserTestsPath();
    }

    // Set the default user - however... this is only useful if you will be
    // using the Dusk type login. It's worth reviewing the Laravel Dusk
    // trait InteractsWithAuthentication to combine with your app.
    protected function user()
    {
        return parent::user();
    }
}

Now create a your tests:, _(*11)

<?php

namespace Application\Tests\Browser;

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

class ExampleTest extends DuskTestCase
{
    /** @test * */
    public function it_can_browse_a_site()
    {
        $this->browse(function (Browser $browser) {
            $browser->visit('/')->assertSee('Klever');
        });
    }
}

Run your tests as part of your testsuite, or separate them out to run on their own (since browser tests can be slow)., _(*12)

Dusk documentation can be found here, _(*13)

Authentication

If you are able to add Dusk Login routes to your application, and for those to be secure, you will be able to use the standard dusk login, loginAs, logout and other methods., _(*14)

If that is not possible, you can leverage the 'Macroable' nature of the Browser class to add custom methods at runtime. Take care to not try to overwite an existing method on the Browser class., _(*15)

For example:, _(*16)

<?php
    // In your testing bootstrap file.

    \Laravel\Dusk\Browser::macro('customLoginAs', function ($user, $pass) {
        $this->browse('login_url')
            ->type('username', $user)
            ->type('pasword', $pass)
            ->press('Login');
    });

Chrome Version

If you receive an error containing information about the Chrome version (e.g. Chrome version must be between 70 and 73), _(*17)

Please run vendor/bin/dusk-updater update, _(*18)

For further information please see the Dusk Updater project, _(*19)

Contributing

Contributions are welcome and will be fully credited. We will accept contributions by Pull Request., _(*20)

Please:, _(*21)

• Use the PSR-2 Coding Standard
• Add tests, if you’re not sure how, please ask.
• Document changes in behaviour, including readme.md.

Testing

We use PHPUnit, _(*22)

Run tests using PHPUnit: vendor/bin/phpunit, _(*23)