- Is ongr/testing-bundle compatible with Laravel?
- No. It is a Symfony bundle built for ONGR ElasticsearchBundle functional tests, and it ships no Laravel service provider, configuration, facades, or test harness integration. Treat it as incompatible with a standard Laravel application. The only realistic use is as a reference for fixture ideas.
- Can I install ongr/testing-bundle in a Laravel project with Composer?
- You should not. The package is archived and its last release was in 2014, so Composer resolution against modern Laravel and PHP versions will likely fail. Even if it installs in a legacy environment, it will not wire into Laravel's testing stack. Avoid adding it as a dependency.
- What does ongr/testing-bundle actually provide?
- It is a Symfony testing bundle that streamlines functional testing for applications built on ONGR Elasticsearch bundles. It provides helpers and utilities for setting up test environments, managing Elasticsearch indices, and includes data fixtures and example ESB documents. Those features are tied to Symfony and ONGR conventions, not Laravel.
- Is ongr/testing-bundle still maintained?
- No, it is deprecated and archived. The last release dates to 2014, with no active maintenance, no PHP 8.x guarantees, and no Laravel support. Any code you adopt immediately becomes internally owned. Upstream support and community ecosystem are effectively absent.
- Does ongr/testing-bundle support Laravel 10 or Laravel 11?
- No. The package predates modern Laravel by many years and targets legacy PHP 5.x-era Symfony and ONGR constraints. Laravel 10 and 11 with PHP 8.2+ should be treated as incompatible unless proven otherwise in a disposable spike. There is no Laravel service provider or version constraint for modern frameworks.
- Can I use ongr/testing-bundle with PHP 8.2 and modern Elasticsearch?
- Not reliably. The bundle's legacy Symfony and ONGR dependencies make PHP 8.2 compatibility unlikely, and its example document schemas may target older Elasticsearch versions. You would need to validate every fixture and query against your target Elasticsearch client and version. In most cases it is faster to recreate the fixtures natively.
- What Laravel alternatives should I use for Elasticsearch test fixtures?
- Use PHPUnit or Pest with Laravel model factories, seeders, and a dedicated test index or Elasticsearch test container. Laravel-native fixtures keep tests fast, reproducible, and compatible with your application's client version. This approach avoids Symfony bootstrapping and legacy dependency conflicts.
- Can I copy the example ESB documents from ongr/testing-bundle into Laravel tests?
- Possibly, but only as static assets. The repository is MIT licensed, so review the license and confirm the example documents add unique schema coverage before copying them. You can convert them to JSON or YAML fixtures and load them through Laravel-native seeders. Do not install the bundle just to access those files.
- How do I set up Elasticsearch test indices in Laravel without this bundle?
- Create a test-only Elasticsearch index or container and manage it through Laravel test setup hooks. Use model factories or seeders to load known fixture documents, then assert queries against that controlled index. Clean or recreate the index between test runs to keep results deterministic. This replaces the bundle's index-management helpers with standard Laravel tooling.
- What risks come with adding ongr/testing-bundle as a dev dependency?
- You risk Composer conflicts, missing Symfony bundle bootstrapping, PHP and Elasticsearch version mismatches, stale ESB document schemas, and CI failures after framework upgrades. It is test-only, so production blast radius is limited, but upgrade and maintenance risk remain high. Since it has zero upstream maintenance, your team owns any fixes immediately.