Weave Code
Behat Laravel Extension Laravel Package
laracasts/behat-laravel-extension
A Behat extension that boots your Laravel application inside feature tests, giving step definitions access to the container, facades, database helpers, and configuration so you can write BDD-style acceptance tests.
Laravel extension for Behat functional testing.
Frequently asked questions about Behat Laravel Extension
- What does laracasts/behat-laravel-extension actually do?
- It is a thin Behat extension that boots a Laravel application inside feature tests so that Gherkin step definitions can use the framework. Once booted, your contexts gain access to the Laravel container, facades, database helpers, and configuration. It is a bridge between Behat 3.x and Laravel, not a browser automation tool or a full end-to-end testing framework. Its main use case is BDD-style acceptance testing for legacy Laravel applications that already rely on Behat.
- How do I install and configure laracasts/behat-laravel-extension?
- You add the package with Composer, register the extension in your behat.yml under the extensions key, and create or extend a Laravel-aware context for your step definitions. You also need a testing environment with an isolated database and a clear seed strategy so feature runs do not touch development data. Because the last release is from 2018, pin your Composer constraints and verify the Behat extension discovery works on your target versions. A time-boxed spike on a branch is the safest way to confirm the bootstrap behaves as expected.
- Which Laravel and PHP versions does this Behat extension support?
- The package is aimed at the Laravel 5.x era and Behat 3.x, with its release history stopping in 2018. It likely predates modern Laravel kernel and container signatures as well as current Behat extension APIs, so Laravel 10 and 11 and PHP 8+ support is not guaranteed. Treat any modern-version adoption as unproven until you run a compatibility spike against your exact PHP, Laravel, and Behat matrix. Expect to maintain an internal fork or apply patches if you need current framework support.
- Is laracasts/behat-laravel-extension compatible with Laravel 10 or 11 and PHP 8?
- Probably not without changes. The package has not had a release since 2018 and likely predates current Laravel bootstrap behavior, container signatures, and Behat extension APIs. PHP 8+ error handling and framework upgrades add further risk. Run composer why-not, a PHP version matrix, and a representative acceptance scenario before assuming compatibility.
- How do I access the Laravel container and facades inside Behat step definitions?
- The extension boots the Laravel application for you, so your Laravel-aware context can reach the container, facades, database helpers, and configuration directly from step definitions. That lets you resolve services, call Eloquent models, and assert application state without manually bootstrapping the framework in each context. Keep this access behind a thin adapter or base context so you can swap the extension later without rewriting all your feature files. Verify that your service providers boot cleanly outside an HTTP request before relying on this in CI.
- How should I handle database migrations, seeding, and isolation with Behat and Laravel?
- Configure a dedicated testing environment with its own database connection so Behat runs never touch development or production data. Decide up front whether you will migrate fresh, wrap scenarios in transactions, or reseed between features, and make that consistent across local runs and CI workers. Parallel CI workers need separate database names or schemas to avoid collisions. The package itself does not solve test data isolation, so this remains your responsibility.
- Is laracasts/behat-laravel-extension still maintained?
- No. The last release was in 2018, the package has a narrow adoption base of around 260 stars, and there is no active upstream release cadence. The MIT license removes legal friction but not compatibility or support risk. Plan to own a fork, dependency pins, and upgrade patches if you adopt it, rather than assuming community maintenance.
- Can this package replace PHPUnit, Pest, or Laravel Dusk?
- No. It is a narrow Behat-to-Laravel bridge for Gherkin acceptance tests and is not a replacement for PHPUnit or Pest, nor is it a browser automation tool. If you need browser-level behavior, you still need Mink, Dusk, or Playwright alongside it. For greenfield Laravel projects, Pest or PHPUnit feature tests plus Dusk or Playwright are lower-risk defaults unless BDD is a hard requirement.
- What are the alternatives to laracasts/behat-laravel-extension?
- If Gherkin is mandatory, evaluate a maintained fork of this extension or Codeception, which has broader Laravel support and active maintenance. If BDD is not a hard business requirement, Pest and PHPUnit feature tests cover most application behavior with far less maintenance burden. Use Dusk or Playwright when you specifically need browser-level end-to-end coverage.
- What are the main risks and best practices for adopting this package in production CI?
- The main risks are PHP 8+ incompatibility, Laravel version incompatibility, Behat extension API drift, fragile application bootstrap, and hidden coupling to old Laravel testing behavior. Keep the package behind an internal adapter or base context, pin Composer constraints, and run a time-boxed compatibility spike on both your oldest supported and target framework versions. Define your CI database reset and seed strategy, isolate parallel workers, and document exit criteria in case the package blocks a framework upgrade. Budget explicit internal ownership for a fork rather than relying on upstream.
Weaver
How can I help you explore Laravel packages today?