Weave Code
Dusk Dashboard Laravel Package
beyondcode/dusk-dashboard
Dusk Dashboard gives Laravel Dusk browser tests a web dashboard. Review test runs and pass/fail results, inspect screenshots and console output, and monitor your end-to-end suite from one place to debug failures faster.
A beautiful dashboard for your Laravel Dusk tests
Frequently asked questions about Dusk Dashboard
- What is beyondcode/dusk-dashboard and what does it do?
- It is a Laravel package that adds a web-based dashboard on top of Laravel Dusk, so you can trigger browser tests from the browser instead of recalling Artisan commands. The dashboard shows per-test pass/fail results, durations, failure details, console output, and screenshots captured during failing tests, and it lets you re-run individual tests or the whole suite. It is a development and debugging tool only, not a production feature.
- How do I install and launch Dusk Dashboard?
- Install it as a dev dependency with composer require --dev beyondcode/dusk-dashboard, then launch the dashboard with the php artisan dusk:dashboard command. It fits into an existing Dusk setup, so your tests and Dusk configuration stay where they are. You can also publish the package config if you need to change defaults; check the published config file for the route and environment options.
- Does Dusk Dashboard need a queue worker or websocket server for live output?
- The dashboard runs tests on demand and surfaces output as the run progresses, but it does not require a separate websocket server or queue worker to function. Whether live updates arrive via polling or a streamed response depends on the package's implementation, so verify the transport in the source of the version you pin. In practice the only hard requirement is a working Dusk setup with a browser driver available on the machine running the dashboard.
- Which Laravel and PHP versions does beyondcode/dusk-dashboard support?
- The only release artifact available is 2.0.0, published in May 2020 with a note about Laravel 7 support, which implies Symfony 5 and PHP 7.2.5 or newer. The repository is archived, so there is no later release widening those constraints. Treat Laravel 6 and 7 as the realistic target and confirm the exact constraints in composer.json before committing.
- Can I use Dusk Dashboard with Laravel 8, 9, 10, or 11?
- Not officially. Because the package is frozen at a Laravel 7-era release, a modern Laravel application will typically hit a Composer dependency conflict rather than a runtime error, so this is a stack-selection gate rather than an integration task. Check Packagist and GitHub for community forks that lift the framework constraints, and review any fork's diff before trusting it. Downgrading Laravel just to use the dashboard is not worth it.
- Is Dusk Dashboard safe to run in production?
- No, it is a dev-only package and should never be reachable in production. A route that can execute browser tests on demand and serve screenshots, console logs, and browser exceptions is an unauthenticated window into your application, and screenshots often capture seeded data, tokens in URLs, and personal information. Confirm from the source that route registration is environment-gated, then add your own local/testing gate and an automated test asserting the route is not registered outside development.
- Should dusk-dashboard be installed with --dev in a Laravel application?
- Yes, it belongs in require-dev and only ever in require-dev. There is no reason for the dashboard route or its dependencies to be present in a production build, and keeping it out of require keeps your deployed dependency surface minimal. This also prevents an accidental route registration from becoming a live exposure if environment gating is ever misconfigured.
- Can I inspect failure screenshots and console output in the dashboard?
- Yes. Dusk already writes screenshots and console output for failing tests to disk, and the dashboard surfaces those artifacts alongside the test result that produced them, including browser exceptions and assertion details. This is convenient for quick triage, but it is largely a viewer over files Dusk already creates, so the same artifacts can also be archived by your CI provider. Confirm where the package reads them from and whether that directory contains regulated data before sharing access.
- How do I re-run a failed test from the dashboard?
- The dashboard exposes per-test re-run controls and a way to execute the full suite again, so you can iterate on a single failing browser test without leaving the interface. Behind that button the package triggers a test run on the server, so on any shared environment make sure only trusted developers can reach it. If you care about how the run is invoked, inspect the endpoint implementation to see which command is executed and with what arguments.
- Is beyondcode/dusk-dashboard still maintained, and what are the alternatives?
- It is effectively abandoned: the repository is archived, there has been no release since 2.0.0 in 2020, and there is no upstream patch path for PHP upgrades, security issues, or Chromedriver changes. If you need the same capability on a modern stack, use Laravel Dusk directly with CI artifact archiving for screenshots and logs, or evaluate actively maintained browser testing tools such as Pest's browser testing or Playwright. Keep the dashboard only where a legacy Laravel 6 or 7 app already depends on a Dusk suite.
Weaver
How can I help you explore Laravel packages today?