- Can I use halleck45/behat-wizard-bundle in a Laravel application?
- Not directly. It is a Symfony bundle that depends on a Symfony kernel, BundleInterface registration, and the Symfony DI container, so Laravel has nothing to boot it with. Composer may install the code, but there is no ServiceProvider, config file, or facade to register. Treat any use as a separate sidecar app or a rewrite, not a package install.
- Does Behat Wizard Bundle support Laravel 10 or 11?
- No. The bundle targets Symfony 2.x-era stacks with PHP 5.x/7.0 constraints, which hard-conflict with Laravel 10/11 on PHP 8.2+. There is no Laravel version support because it was never built for Laravel. Expect Composer dependency conflicts if you try to add it to a modern Laravel composer.json.
- How do I install halleck45/behat-wizard-bundle?
- Install it with Composer inside a Symfony application and register the bundle in your Symfony kernel, following the repository README. It is not installable as a Laravel package in the usual sense. For Laravel teams, the realistic path is a pinned standalone Symfony container rather than adding it to the app's composer.json.
- Is Behat Wizard Bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, despite often appearing in Composer searches developers run for Laravel tooling. It ships no Illuminate contracts, facades, or Laravel service provider. The framework-family mismatch is the main reason to avoid treating it as a drop-in dependency.
- What are the PHP and Symfony version requirements for Behat Wizard Bundle?
- Expect Symfony 2.x-era constraints and PHP 5.x/7.0, based on its Assetic-era asset handling and Symfony Forms usage. Exact constraints should be verified in composer.json before any commitment, since the repository shows no visible release cadence. Those constraints are the gate for whether a sidecar container is feasible.
- Is it safe to expose the Behat wizard UI in production?
- No. The tool writes .feature files and can trigger Behat runs, which means file writes plus process execution, a remote-code-execution vector if it ever escapes localhost. Bind it to 127.0.0.1 only, keep it on a dev Docker profile, and never put it behind a shared hostname. It has no visible authentication or authorization layer.
- Where does the wizard write .feature files?
- It is designed to create and edit .feature files in a Behat/Symfony project layout, typically under a features directory. Laravel projects often keep features at the repository root rather than under a bundle, so verify it tolerates your layout. Also confirm writes are atomic and git-aware before trusting it with real test files.
- How do I run Behat Wizard alongside a Laravel app using Docker?
- Run the bundle in a pinned php:7.x Symfony container on a docker-compose dev profile and mount your Laravel project's ./features directory as a volume. Keep the legacy PHP runtime out of the app image and out of the app's composer.json. Publish the port to 127.0.0.1 only. This sidecar approach needs zero changes to the Laravel application.
- What are the alternatives to Behat Wizard Bundle for BDD in Laravel?
- Most teams get the same value from IDE Behat/PHPStorm plugins, behat --format=pretty output, or a Pest-based BDD flow. These avoid a legacy Symfony runtime and a web surface that shells out. The bundle's main draw is a GUI for product owners, so weigh whether that UI is genuinely load-bearing before adopting it.
- Is halleck45/behat-wizard-bundle maintained?
- Signals point to effectively unmaintained: 91 stars, zero dependents, and no visible release cadence. If you adopt it, pin to a commit SHA, vendor-patch as needed, and assume you become the maintainer. Budget roughly one to two engineer-weeks if you decide to port the UI to Laravel with Blade and a Process-based runner.