Download the PHP package winter/wn-dusk-plugin without Composer
On this page you can find all versions of the php package winter/wn-dusk-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package wn-dusk-plugin
Dusk Plugin
Integrates Laravel Dusk browser testing into Winter CMS, providing Winter CMS and plugin developers with the tools to run automated tests on a fully functional Winter CMS instance through a virtual browser.
Note: This plugin is intended to be used for development purposes only. Configured improperly, it can allow users to circumvent authentication and sign in as any user. This plugin should be specified as a development dependency (ie.
require-dev
) only.
Getting started
To install the plugin, you may install it through the Winter CMS Marketplace, or you may install it using Composer:
Then, run the migrations to ensure the plugin is enabled:
To run the browser tests, you must install the Chrome web-driver and have the Google Chrome browser installed on the machine running the tests. The web-driver can be installed by running the following command:
Running the tests
By default, the browser tests are configured to run the tests against a website served by the in-built Laravel web server. You may start this server by running the following:
To start the browser tests, run:
This will execute all available browser tests in all enabled plugins on your Winter CMS installation. If you would like to run the tests for one plugin only, you may add the plugin code as an argument:
As a shortcut after running the tests, you may re-run the failed tests by executing the following command:
Creating browser tests for your plugin
The Dusk plugin makes it a breeze to create browser tests for your own plugin.
Browser test classes should reside in the tests/browser folder of your plugin. Each test class file should ended with Test.php
to indicate it is a class of test cases, and should extend the Winter\Dusk\Classes\BrowserTestCase
class.
For example, a blog plugin may wish to create a BlogTest.php file with the following content:
Each test method in the class should be prefixed with test to denote that it is a test case.
To run the browser tests for your plugin, simply run the following: