Alice Bundle Extension Laravel Package

Product Decisions This Supports

• Build vs. buy for test-data tooling. This package answers a narrow question: do we write our own Behat hooks to load Alice fixtures per scenario, or adopt an existing extension? It exists to remove that glue code, so it's relevant only if fixture-driven BDD is already on the roadmap.
• Test-infrastructure roadmap input. If the team runs Behat against a Symfony app using HautelookAliceBundle, adopting this reduces per-scenario boilerplate (database reset + fixture load) and shortens the path to reliable acceptance tests. If Behat isn't already in the stack, this package is not a reason to adopt Behat.
• Feature/QA enablement. Supports teams writing scenario-level fixtures in YAML/JSON instead of hand-maintained seed scripts — better readability for QA and product folks reviewing test data.
• A "vendor, don't depend" decision. The archived status, single 2016 release, and zero dependents make this a reference implementation to copy into the repo, not a supply-chain dependency to standardize on. That distinction is itself the product decision.
• Scope correction for Laravel. Despite being framed as a Laravel/PHP package, HautelookAliceBundle is a Symfony bundle and this extension is Symfony+Behat glue. For a Laravel roadmap, this does not support any decision — Laravel teams should use Eloquent model factories and seeders, or a maintained Laravel-specific fixture library. This package should be explicitly ruled out in a Laravel context rather than evaluated on merit.

When to Consider This Package

Adopt (or vendor) when:

• The application is Symfony, already uses HautelookAliceBundle, and already runs Behat suites.
• You want fixtures loaded automatically per scenario without maintaining custom BeforeScenario hooks.
• You accept pinning an unmaintained 2016-era package and are prepared to fork it for PHP version compatibility.

Look elsewhere when:

• You're on Laravel. Use model factories/seeders or a maintained Laravel fixture package; this won't integrate.
• You need active maintenance, security patching, or PHP 8.x support. No releases since June 2016, archived repo, 36 stars, 0 dependents — assume you own the code the moment you adopt it.
• You're not already on Behat. Don't introduce a BDD framework to justify a small glue extension.
• The integration surface is small enough to reimplement. Since the extension is thin, a first-party implementation is often a better long-term bet than a vendored abandoned dependency.
• You require vendor support or a documented upgrade path for compliance/audit reasons.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed integration helper between two testing tools, and it has been abandoned since 2016 with no maintainers and no downstream dependents. It is not a strategic dependency and should not appear on a roadmap. If our team is already doing Behat-based acceptance testing on Symfony with AliceBundle fixtures, we can copy the relevant glue into our own codebase in a day or two and own it outright. Recommendation: treat as a code sample, not a product to adopt; do not budget for support or upgrades from it.

To engineering: It's a thin Behat extension that wires HautelookAliceBundle's fixture loading into Behat contexts so scenarios get fresh data without hand-rolled hooks. It's readable and easy to vendor. Caveats: archived, one release from 2016, zero dependents — expect PHP-version drift and plan to fork. If we're on Laravel, stop here; this doesn't apply and factories/seeders are the right answer. If we're on Symfony + Behat + AliceBundle, spend an afternoon auditing it against our PHP version before deciding between vendoring and reimplementing.