- What is richcongress/recurrent-fixtures-test-bundle used for?
- It is a lightweight Symfony testing helper for loading and reusing recurrent fixture sets across functional tests. It integrates with the Symfony test kernel and PHPUnit workflows, helps reset and reload fixture data, and keeps test setup configuration-driven. It is intended for test environments rather than production runtime.
- Does richcongress/recurrent-fixtures-test-bundle work with Laravel?
- It is described as a Symfony testing helper, not a native Laravel package. The TPM assessment discusses Laravel/PHP relevance mainly through doctrine/dbal constraint compatibility, not proven Laravel runtime support. Treat Laravel use as conditional until you verify kernel integration, test bootstrapping, and DBAL behavior in your app.
- How do I install richcongress/recurrent-fixtures-test-bundle?
- Install it with Composer using the package name richcongress/recurrent-fixtures-test-bundle, but treat it as a Symfony bundle first. In a Laravel app, confirm bundle or kernel integration and test bootstrapping before assuming native Laravel support. Pin v0.1.12 in a pilot rather than floating to ^0.1.
- Which Laravel, PHP, and database driver versions are supported?
- The provided material does not publish a Laravel, PHP, or database driver support matrix. v0.1.12 only confirms widened doctrine/dbal support to v2.x and v3.x in Composer. Require a documented matrix and CI evidence before standardizing on it.
- Does v0.1.12 support doctrine/dbal 2.x and 3.x at runtime?
- No. The release note confirms only a Composer constraint change, not runtime coverage. DBAL v3 includes breaking API and behavioral changes, so validate against both major versions. Treat adoptability as conditional until tests prove it.
- Is doctrine/dbal required or optional for this bundle?
- The context does not state whether doctrine/dbal is optional or required. The release widens DBAL constraints, which matters when DBAL is present directly or transitively. Check composer.json and dependency usage before adopting it.
- How do I reset and reload recurrent fixtures between tests?
- The overview says the bundle helps reset and reload fixture data between tests and keeps setup configuration-driven. Exact configuration keys are not included in the provided excerpt. Follow the repository README and test kernel setup for your Symfony or Laravel test bootstrap.
- Can I use this bundle in production or only in test environments?
- No. The overview says it is designed for test environments, not production runtime. Use it only in test suites and keep production dependencies free of test-only tooling. Validate lockfile impact before deployment.
- How should I validate DBAL 3 compatibility before adopting v0.1.12?
- Inventory DBAL constraints with Composer, then run the application test suite against DBAL 2.x and 3.x where feasible. Pilot v0.1.12 in a non-production environment with representative database drivers. Pay attention to schema introspection, column alteration, platform detection, and result APIs. Document rollback to the prior package and DBAL combination.
- What alternatives exist for reusable Laravel fixtures, and how is this bundle maintained?
- For Laravel, native factories and seeders are common alternatives; for Symfony, DoctrineFixturesBundle and custom fixture loaders are options. This bundle's niche is recurrent fixture reuse across functional tests. Because it is pre-1.0 v0.1.12, review maintenance activity and CI evidence before standardizing.