Download the PHP package unglud/dusker without Composer
On this page you can find all versions of the php package unglud/dusker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download unglud/dusker
More information about unglud/dusker
Files in unglud/dusker
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package dusker
dusker
Stand-alone Laravel Dusk test suit, which does not require Laravel framework itself.
Laravel Dusk provides an expressive, easy-to-use browser automation and testing API. By default, Dusk does not require you to install JDK or Selenium on your machine. Instead, Dusk uses a standalone Chrome driver. However, you are free to utilize any other Selenium driver you wish.
Installation
To get started, you should add the unglud/dusker Composer dependency to your project:
Next, you need to copy all necessary files to your working directory. The command below will do it for you. It creates (or use existing) tests directory and put files there. Also, it copies artisan console utility to your project root directory. If you already have this file, it will be overwritten!
The file .env.dusk will be in your project root as well, which you will need rename to .env or copy it content to your existing one.
If you would like these files to update automatically each time you update this package, you can add this to your composer.json file:
As you notice file .env.dusk not included there to simplify things.
After installing the package, Artisan commands will be available from your root project. Run the dusk:install Artisan command:
Now try to run test to make sure everything works
How to use
After this part you can use official documentation for Dusk on the Laravel website, `cuz it will work exactly as it was designed by Taylor Otwell.
Authentication
Often, you will be testing pages that require authentication. You can use Dusk's loginAs method in order to avoid interacting with the login screen during every test. The loginAs method accepts a user login and password:
After using the loginAs method, the user session will be maintained for all tests within the file.
Authentication Setup
Since we do not have access to native Auth and Router from Laravel, because we use it without Laravel we need to setup login functionality.
In .env you should specify LOGIN_ENDPOINT -- path to your public directory where Dusker will copy the file which will be accessible from a browser. By default its http://example.com/_dusker/login.php. Second LOGIN_IMPLEMENTATION -- path to your class, which utilize logic of your project allowing Authentication. You can use /tests/LoginManagerExample.php as an example of how it should look.
License
Dusker is released under the MIT Licence. See the bundled LICENSE file for details.
All versions of dusker with dependencies
composer/composer Version ^1.0
illuminate/config Version ^5.5
illuminate/container Version ^5.5
illuminate/events Version ^5.5
illuminate/filesystem Version ^5.5
illuminate/support Version ^5.5
laravel/dusk Version ^2.0
phpunit/phpunit Version ^6.0
symfony/filesystem Version ^3.3
symfony/http-kernel Version ^3.3
vlucas/phpdotenv Version ^2.4