Weave Code
Testing Bundle Laravel Package
kununu/testing-bundle
Kununu Testing Bundle provides reusable helpers and utilities for testing Symfony applications, simplifying test setup, mocking, and assertions so teams can write cleaner, more maintainable PHPUnit tests.
kununu/testing-bundle is a Symfony testing bundle that reduces boilerplate when writing functional and integration tests. It provides reusable test-case foundations and container-aware helpers so teams can focus on behavior instead of setup, while staying aligned with Symfony’s testing conventions.
- Base test cases for Symfony kernel and container testing
- Helpers for retrieving and replacing services in tests
- Utilities for mocking dependencies and isolating behavior
- Configuration support for consistent test environments
- Lightweight integration with existing PHPUnit/Symfony workflows
Frequently asked questions about Testing Bundle
- Is kununu/testing-bundle compatible with Laravel?
- No. kununu/testing-bundle is a Symfony bundle, not a Laravel package. It depends on Symfony bundle discovery, config/bundles.php wiring, DependencyInjection extensions, and compiler passes, none of which Laravel provides. Composer may install it, but it will not function as a testing layer inside a Laravel test suite.
- Can I install kununu/testing-bundle in a Laravel application via Composer?
- Technically Composer can install it if your PHP and dependency constraints match. That does not make it usable in Laravel: the package expects a Symfony kernel and bundle configuration. There is no Laravel service provider or bundle loader to activate its helpers. Treat installation as possible but integration as effectively unavailable.
- What testing features does kununu/testing-bundle provide?
- The bundle provides base test cases, fixture loading, mock helpers, and ready-made assertions aimed at Symfony applications. Those helpers are meant to reduce boilerplate around Symfony's KernelTestCase and Doctrine-backed fixtures. Laravel already covers similar ground with RefreshDatabase, model factories, and fake facades. The feature overlap is conceptual, not code-compatible.
- Does kununu/testing-bundle work with PHPUnit 10 or 11?
- The provided assessment does not confirm PHPUnit 10 or 11 support; it explicitly flags checking whether the package supports those majors or is pinned to 9.x. Test-infrastructure dependencies have outsized blast radius because a PHPUnit major break can redline your entire CI pipeline. Inspect composer.json constraints and recent commits before relying on it.
- What are Laravel alternatives to kununu/testing-bundle for fixtures and test helpers?
- Use Laravel's built-in testing tools: RefreshDatabase or DatabaseTransactions for isolation, model factories and seeders for fixtures, Http::fake and Bus::fake for boundary stubbing, and Pest datasets or PHPUnit data providers for parameterization. For shared helpers, create a small internal base TestCase and traits. Those are maintained with Laravel and avoid a second testing mental model.
- Does kununu/testing-bundle require Doctrine for fixture loading?
- According to the assessment, fixture loading almost certainly routes through Doctrine, likely doctrine/data-fixtures and possibly nelmio/alice. Laravel's Eloquent does not share that persistence layer, so Doctrine fixtures will not load your Eloquent models. Verify the composer requirements, but plan for fixture loading to be unusable standalone in Laravel.
- How do I migrate kununu/testing-bundle patterns to Laravel?
- Port the patterns, not the code. Reimplement attractive ideas as a small internal Laravel package: a base TestCase with pre-wired auth and HTTP assertions, a fixture loader built on factories plus a seeder abstraction, and a trait for database reset and deterministic fixture ordering. This keeps you on Laravel-native primitives. It also avoids depending on an unmaintained Symfony bundle.
- Is kununu/testing-bundle actively maintained?
- Maintenance signals are weak: the assessment cites 8 stars, 0 dependents, and single-vendor stewardship. It also flags a future-dated 2026-09-15 release timestamp as anomalous metadata noise. MIT licensing removes legal friction but not the risk of tag-and-abandon. For test infrastructure, verify commit cadence over the last 12 months before any commitment.
- What is the Composer type of kununu/testing-bundle and why does it matter for Laravel?
- Check the composer.json type field. If it is symfony-bundle, the Laravel discussion ends immediately because Laravel has no bundle loader or compiler pass pipeline. A library type would still need Symfony-free helper classes to be extractable. The assessment treats the type as the deciding question.
- Can I use only the helper classes from kununu/testing-bundle in Laravel?
- Only individual helper classes that avoid Symfony container and kernel coupling might be extractable. Fixture loading is almost certainly Doctrine-bound, so that part will not transfer to Eloquent. The viable slice is narrow and conceptual. Reimplementing the useful patterns inside your Laravel codebase is lower risk than adding this dependency.
Weaver
How can I help you explore Laravel packages today?