PHPackages                             bibby/dusk-failures - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. bibby/dusk-failures

ActiveLibrary[DevOps & Deployment](/categories/devops)

bibby/dusk-failures
===================

Package to add dusk:failures command to Laravel. Emails screenshots and console errors of all failed Dusk tests.

0.2.0(6y ago)2693MITPHPPHP ^7.2

Since Nov 17Pushed 6y ago2 watchersCompare

[ Source](https://github.com/andrewjamesbibby/dusk-failures)[ Packagist](https://packagist.org/packages/bibby/dusk-failures)[ Docs](https://github.com/andrewjamesbibby/dusk-failures)[ RSS](/packages/bibby-dusk-failures/feed)WikiDiscussions master Synced 5d ago

READMEChangelogDependencies (1)Versions (4)Used By (0)

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
------------------------

[](#installation--setup)

You can install this package via composer:

```
composer require bibby/dusk-failures

```

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.

```
DUSK_FAILURES_RECIPIENT=youremail@example.com

```

Publish
-------

[](#publish)

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

```
php artisan vendor:publish

```

Usage
-----

[](#usage)

To use simply run:

```
php artisan dusk:failures

```

Options
-------

[](#options)

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

```
php artisan dusk:failures --build=

```

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.

```
php artisan dusk:failures --zip

```

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

```
php artisan dusk:failures --console.

```

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:

```
after_failure:
  - php artisan dusk:failures --build=$TRAVIS_BUILD_WEB_URL --zip --console

```

Credits
-------

[](#credits)

Andrew James Bibby

License
-------

[](#license)

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

###  Health Score

25

—

LowBetter than 37% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity44

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 62.5% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~3 days

Total

3

Last Release

2366d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/e930ae664b8754e064bab667c522085706e76a514bb70b93efcf497ae1417202?d=identicon)[bibby](/maintainers/bibby)

---

Top Contributors

[![andrewjamesbibby](https://avatars.githubusercontent.com/u/7108512?v=4)](https://github.com/andrewjamesbibby "andrewjamesbibby (10 commits)")[![andrew-bibby](https://avatars.githubusercontent.com/u/13904941?v=4)](https://github.com/andrew-bibby "andrew-bibby (6 commits)")

---

Tags

laravelciduskbibby

### Embed Badge

![Health badge](/badges/bibby-dusk-failures/health.svg)

```
[![Health](https://phpackages.com/badges/bibby-dusk-failures/health.svg)](https://phpackages.com/packages/bibby-dusk-failures)
```

###  Alternatives

[spatie/laravel-prometheus

Export Laravel metrics to Prometheus

2651.3M6](/packages/spatie-laravel-prometheus)[renoki-co/laravel-php-k8s

Just a simple port of renoki-co/php-k8s for easier access in Laravel.

88218.2k](/packages/renoki-co-laravel-php-k8s)[innocenzi/deployer-recipe-forge

Seamless zero-downtime deployment on Forge with Deployer

1916.6k](/packages/innocenzi-deployer-recipe-forge)[thebytelab/vapor-multi-region-deploy

An artisan command to assist deploying your Laravel Vapor app to multiple AWS regions

162.2k](/packages/thebytelab-vapor-multi-region-deploy)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)