- Does i22/functional-test-bundle work with Laravel?
- No. It is a Symfony bundle built around Symfony's test kernel, bundle registration, and hautelook/alice-bundle, while Laravel boots its own test case and uses Eloquent by default. Composer may resolve the package, but nothing in a Laravel app will bootstrap or integrate it. Treat it as a design reference rather than a dependency.
- How do I install i22/functional-test-bundle in a Laravel project?
- You generally should not. Adding it to require-dev can pull 2019-era Symfony, PHP 7.x, PHPUnit 6/7, and Doctrine/Alice constraints that conflict with current Laravel. There is no Laravel service provider or test-case hook to register. If you need fixture-loading ideas, copy the pattern into an internal trait instead.
- What Laravel versions are supported by i22/functional-test-bundle?
- None are officially supported. The package targets Symfony applications, and its 2019 constraints predate Laravel 10/11 requirements such as PHP 8.1+ and PHPUnit 10/11. Expect hard Composer conflicts. Do not assume modern Laravel compatibility.
- What is i22/functional-test-bundle used for?
- It bundles reusable Symfony functional-test utilities: base test cases, HTTP request and response assertion helpers, and fixture-set loading through hautelook/alice-bundle. It is meant to reduce boilerplate around booting the Symfony test kernel and asserting end-to-end behavior. The portable value for Laravel teams is its patterns, not the code.
- Is i22/functional-test-bundle still maintained?
- No meaningful maintenance is evident. The last release was 2019-08-27, with zero stars and zero dependents in the assessment, and no upstream triage or security response. That creates high technical risk. Avoid it for new work.
- What are the best alternatives to i22/functional-test-bundle for Laravel?
- Use Laravel's built-in testing stack: Illuminate\Foundation\Testing\TestCase, RefreshDatabase, model factories, seeders, and HTTP assertion helpers. For declarative fixture files, build a small internal trait that reads YAML or JSON and hydrates through factories; nelmio/alice core plus an Eloquent persister is an option if the data-definition format matters. For Symfony projects, zenstruck/foundry is the maintained successor.
- Does i22/functional-test-bundle support PHPUnit 10 or PHPUnit 11?
- Very unlikely. It was built for PHPUnit 6/7-era APIs and base test classes, and there has been no compatibility work since 2019. Modern PHPUnit lifecycle and assertion APIs can break those base classes. Its Composer constraints will also conflict with current PHPUnit versions.
- Does i22/functional-test-bundle require Doctrine ORM?
- It depends on hautelook/alice-bundle, which is wired to Doctrine ORM for persistence. That is a poor fit for Laravel's default Eloquent layer, and the bundle has no Eloquent persister. You would need custom glue even to reuse Alice-style fixtures in Laravel.
- How do I migrate from i22/functional-test-bundle to Laravel testing?
- Do not migrate the dependency; replace the behavior. Add a LoadsFixtures-style trait on top of RefreshDatabase that reads fixture files and creates records through Laravel factories or seeders, then use Laravel's HTTP testing helpers for request and response assertions. If you need Alice-compatible data definitions, use the maintained nelmio/alice core with a custom Eloquent persister, typically 150-250 lines of owned glue.
- Is i22/functional-test-bundle safe to use in production or CI?
- It is a test-only bundle, so it should never be a production dependency. In CI, the bigger issue is abandonment: 2019 constraints, no security response, and brittle PHPUnit integration make failures likely. For Laravel CI, use the framework's own test tooling instead.