Download the PHP package bibby/dusk-failures without Composer

On this page you can find all versions of the php package bibby/dusk-failures. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of bibby/dusk-failures

Informations about the package dusk-failures

Dusk Failures

A simple Laravel Package to enable the emailing of Dusk failure screenshots. This has been built to assist debugging Dusk tests which run on a Continuous Integration service.

During local testing, screenshots for Dusk failures can be easily viewed within a projects screenshot folder. Laravel Dusk tests can take a long time to run so it is much more convenient to pass the running of them to a continuous integration service such as Travis CI.

This command can be used upon failure of any dusk tests. The resulting email will contain the screenshots allowing easier debugging.

Installation & Setup

You can install this package via composer:

`

Then in your .env file ensure you have added the following variable with and replace the value with a suitable email address. Multiple recipients can be comma separated.

`

Publish

If you wish to override the email view or update config settings then publish using:

`

Usage

To use simply run:

`

Options

The 'build' option can be specified. This is useful to indicate in the email which build the failed screenshots belong to:

The 'zip' option will zip and attach the screenshots instead of displaying them inline in the body of the email. This could be preferable if a large number of screenshots are expected.

The 'console' option can be specified which will attach the browser console logs.

Using Travis CI this command can be put in the on_failure block of the travis.yml file and used in combination with Travis environment variables:

`

Credits

Andrew James Bibby

License

The MIT License (MIT). Please see License File for more information.

All versions of dusk-failures with dependencies

PHP Build Version
Package Version
Requires php Version ^7.2
laravel/dusk Version ^3.0|^4.0|^5.0|^6.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package bibby/dusk-failures contains the following files

Loading the files please wait ....