- Is mazarini/test-bundle a Laravel package or a Symfony bundle?
- The package name and mazarini namespace strongly suggest a Symfony bundle rather than a Laravel package. There is no evidence in the metadata of a Laravel ServiceProvider, package discovery configuration, or Laravel-specific integration. Treat it as Symfony-oriented until the composer.json and source code prove otherwise.
- Does mazarini/test-bundle support Laravel package auto-discovery?
- No Laravel auto-discovery support is evident from the available metadata. A Symfony-style bundle will not auto-register through Laravel's package discovery mechanism and will not expose a Laravel ServiceProvider by default. Laravel teams would need manual wiring or should reject it unless framework alignment is confirmed.
- How do I install mazarini/test-bundle with Composer?
- You would typically install it with Composer as a require-dev dependency, for example composer require --dev mazarini/test-bundle, and pin an exact version. Before installing, check Packagist and the repository composer.json for PHP and framework constraints. Do not add it to the production dependency graph.
- What Laravel versions does mazarini/test-bundle support?
- The available metadata provides no Laravel version constraints and no evidence of Laravel support at all. You cannot assume compatibility with Laravel 10, 11, 12, or any other release. Verify the composer.json constraints and test suite before considering adoption.
- What testing use cases does mazarini/test-bundle cover?
- Its declared purpose is to provide fake entities and services that help with tests. It is unclear whether it ships prebuilt fakes and stubs, deterministic entity fixtures, or fixture and seeding utilities. Compare its actual output against Laravel factories, Faker, seeders, and Mockery before adopting it.
- Is mazarini/test-bundle safe to use in production?
- This is a test utility and should be scoped strictly to require-dev and the test autoloader. It must never enter the production dependency graph. GPL-3.0 licensing, minimal adoption, and single-maintainer risk make production use inappropriate without legal and technical review.
- What license does mazarini/test-bundle use, and is GPL-3.0 a problem for Laravel apps?
- The assessment identifies GPL-3.0, a strong copyleft license. Even as a dev-only dependency, whether test code linking against GPL code is a derivative work is legally unsettled. Proprietary or commercially licensed Laravel products should require legal sign-off before adoption.
- How does mazarini/test-bundle compare to Laravel factories, Faker, and Mockery?
- Laravel already ships model factories, Faker integration, database seeders, and Mockery plus fake helpers. This package may overlap heavily with those native tools unless it provides meaningfully distinct boundary fakes or deterministic fixtures. Measure the delta in test setup lines, readability, and runtime before replacing the native toolchain.
- Is mazarini/test-bundle actively maintained and reliable?
- The package has 0 stars, 0 dependents, and a single maintainer, with no evidence of a maintained release cadence. That implies little downstream pressure to keep it current with PHP or framework upgrades. Check the repository for a test suite and CI version matrix before relying on it.
- Can I use mazarini/test-bundle with Eloquent, or does it require Doctrine?
- The metadata does not confirm Eloquent support or rule out Doctrine coupling. Symfony-oriented fake-entity libraries often assume Doctrine entities, which would be largely useless in an Eloquent codebase. Verify its ORM and testing-framework assumptions during a short evaluation spike.