Weave Code
Test Bundle Laravel Package
infinitytracking/test-bundle
A lightweight test bundle from Infinity Tracking designed to validate package structure and integration workflows. It offers a minimal setup for exercising bundle behavior in PHP projects, making it useful as a starting point for testing and development.
Symfony2 Bundle that provides structured test implementation and helpers
Frequently asked questions about Test Bundle
- Is infinitytracking/test-bundle compatible with Laravel 10 or 11?
- No. Despite the package description mentioning Laravel, the codebase is a Symfony 2 bundle. It registers via AppKernel::registerBundles() and extends Symfony's KernelTestCase and WebTestCase, which have no equivalent in Laravel's service provider and test lifecycle. Composer resolution also fails because it constrains Symfony 2.x components and PHP to ranges incompatible with Laravel 10/11.
- How do I install infinitytracking/test-bundle in a Laravel project?
- You generally cannot install it in a modern Laravel project. The package's composer.json pins symfony/framework-bundle and symfony/http-kernel to Symfony 2.x ranges and requires phpunit/phpunit ~5.7, which conflicts with Laravel 10/11 dependencies and PHP 8.1+. A composer require will likely fail with dependency resolution errors, and there is no Laravel service provider for auto-discovery.
- What Laravel versions does this test bundle support?
- None officially. The package is built on the Symfony 2 bundle system and its test base classes extend Symfony\Bundle\FrameworkBundle\Test\KernelTestCase and WebTestCase. Laravel uses Illuminate\Foundation\Testing\TestCase and service providers, so there is no shared contract. The v1.0.1 release only bumps PHPUnit to 5.7 and does not add Laravel support.
- Can I use the test fixtures and assertion helpers in my Laravel tests?
- Only by manually cherry-picking individual helper classes from the tarball. The package is not a Laravel package, so its fixtures, factories, and assertions are tied to Symfony's test harness. There is no auto-discovery or service provider integration, and the code was written against PHPUnit 4/5-era APIs like getMock() and string-match assertContains(). Vendoring may be possible if the license permits, but you would need to adapt the code.
- Is infinitytracking/test-bundle maintained and safe for production use?
- No. The package has zero stars, zero dependents, and no downstream validation. The v1.0.1 release is a single-commit version bump that pins PHPUnit to 5.7, which left security support in February 2019. The underlying Symfony 2 code also carries known advisories, so composer audit would likely fail your supply-chain gate. The maintainer appears active enough to tag a release, but the package is not modernized.
- What is the difference between this bundle and Laravel's built-in testing utilities?
- Laravel's testing utilities are built around Illuminate\Foundation\Testing\TestCase, service providers, facades, and HTTP simulation via the Laravel kernel. This bundle is built around Symfony's AppKernel, DependencyInjection extensions, and YAML/XML service definitions. They bootstrap different kernels, use different environment files, and have different HTTP simulation layers, so there is no shared contract to bridge.
- Why does composer require fail with a PHPUnit conflict?
- The v1.0.1 release explicitly pins phpunit/phpunit to the 5.7 line. Modern Laravel projects run PHPUnit 10/11 or Pest 2/3, so the require-dev constraint creates a hard composer why-not conflict. Even if you force an install, the package also constrains Symfony 2.x components and PHP to versions incompatible with Laravel 10/11.
- Are there better-maintained alternatives for Laravel test fixtures and assertions?
- Yes. Laravel's own testing utilities, PHPUnit, Pest, and packages like Laravel Factories, Faker, and various assertion libraries are actively maintained. If you need reusable fixtures or HTTP assertions, look for packages that explicitly support Laravel 10/11 and PHP 8.1+ and are tested against modern PHPUnit. This bundle is not a viable alternative because it is a Symfony 2 package with no Laravel integration.
- What is actually inside infinitytracking/test-bundle?
- Based on the technical assessment, the package is a Symfony 2 bundle with test base classes extending Symfony's KernelTestCase and WebTestCase. The description mentions fixtures, factories, and assertion helpers, but the codebase was written against PHPUnit 4/5-era APIs and has not been modernized. It is likely a thin wrapper around Symfony's functional testing tools rather than substantive Laravel-specific logic.
- Was infinitytracking/test-bundle ever a Laravel package or a fork of one?
- The repository appears to be a Symfony 2 bundle, not a Laravel package. The composer name and description mention Laravel, but the TPM assessment finds no Laravel service provider, facade, or Illuminate container integration. It may be a minimal bundle created for internal package structure validation, and there is no evidence it is a fork of a better-maintained Laravel testing package.
Weaver
How can I help you explore Laravel packages today?