Weave Code
Mink Debug Extension Laravel Package
lakion/mink-debug-extension
MinkDebugExtension (friends-of-behat/mink-debug-extension) is a Behat extension that logs and debugs Mink data after every failed step, especially useful on CI. With a supported driver it can save screenshots. Configure the log directory, screenshot option, and clean_start.
MinkDebugExtension is a Behat extension that logs and debugs Mink-related data after every failed step, making it especially useful on continuous integration servers like Travis. With a supporting driver, it can also capture screenshots at the moment of failure.
Install via composer require friends-of-behat/mink-debug-extension, then enable it in your Behat profile with a directory for logs.
- Automatic logs after each failed step
- Optional screenshots with supporting drivers
- Configurable output directory (supports
%paths.base%) - Clean start option to wipe old logs on each run
- Simple Behat profile configuration
Frequently asked questions about Mink Debug Extension
- Is this a Laravel package or a Behat extension?
- No, it is not a Laravel package. It has no service provider, facade, config file, or Laravel test runner integration. It is a Behat extension loaded through behat.yml that hooks Mink failures and writes artifacts. In a Laravel app it only helps if you already run Behat and Mink acceptance tests.
- How do I install MinkDebugExtension with Composer?
- Run composer require friends-of-behat/mink-debug-extension as a dev dependency. The repository is FriendsOfBehat/MinkDebugExtension, and the modern package name is friends-of-behat/mink-debug-extension. Then enable it under the extensions key in your Behat profile.
- How do I configure directory, screenshot, and clean_start?
- Under FriendsOfBehat\MinkDebugExtension in behat.yml, set directory to the log path; this option is required to enable the extension. screenshot defaults to false and only works with a supporting driver. clean_start defaults to true and clears previous logs on each Behat run.
- Does it support Laravel 10 or 11, Laravel Dusk, PHPUnit, or Pest?
- It is not tied to Laravel versions because it is not a Laravel package. Support depends on your Behat, Mink, PHP, and driver versions rather than Laravel 10 or 11. It does not integrate with Laravel Dusk, PHPUnit, or Pest.
- Which Mink drivers support screenshots on failure?
- Screenshots require a driver that can capture them, such as Selenium and other screenshot-capable drivers supported since v2.0.0. Goutte and similar drivers produce logs only. Verify the driver used by your Behat suites before enabling screenshot: true or promising screenshots.
- Why did the Lakion namespace stop working after upgrading?
- The original repository was Lakion/MinkDebugExtension, but the installable package is friends-of-behat/mink-debug-extension. The namespace changed from Lakion\Behat\MinkDebugExtension to FriendsOfBehat\MinkDebugExtension in v2.0.0. Old wiki and StackOverflow examples using the Lakion namespace will silently fail to load.
- What changed between v1 and v2 of mink-debug-extension?
- v2 changed the log file extension from .log to .html and removed upload-textfiles, upload-screenshots, and wait-for-port helper binaries. CI scripts calling vendor/lakion/mink-debug-extension/travis/tools/* will break. Upload artifacts natively with actions/upload-artifact or GitLab artifacts instead.
- Can MinkDebugExtension logs contain sensitive data or PII?
- Yes. The extension writes HTML dumps of page source that can include session tokens, emails, and customer data. clean_start true limits accumulation but not content sensitivity. Restrict access to the log directory, set retention, and consider redaction before uploading CI artifacts.
- How can I verify that MinkDebugExtension is working?
- Enable the extension, run your Behat suite, and force one failing Mink step. Confirm that the configured directory contains the expected .html log and, if enabled and supported, a screenshot. The extension's own test suite is run with composer install followed by bin/behat --strict.
- Is MinkDebugExtension maintained, and what should I use instead?
- It is a small, single-maintainer utility with about 204 stars but 0 dependents and a low composite score; the FriendsOfBehat fork carries maintenance after the legacy Lakion era. The license is NOASSERTION, so compliance should verify the LICENSE file before regulated adoption. Alternatives include custom Behat hooks or driver logging for Mink, and Laravel Dusk screenshots or PHPUnit/Pest failure output for Laravel-native suites.
Weaver
How can I help you explore Laravel packages today?