Symfony Functional Testcase Laravel Package

Product Decisions This Supports

• Test-infrastructure roadmap: 1.5.0 sets a hard floor of PHP 8.1 and Symfony 5.4. This is a forcing function for the team’s runtime-upgrade plan—if the product still supports PHP 8.0 or Symfony 5.3, this package can no longer be used in the shared test suite.
• Build vs. buy / keep vs. replace: The deprecation of getDependencyInjectionContainer() in favor of Symfony’s native getContainer() signals that the package is converging on framework-native behavior. PMs should decide whether to keep the thin wrapper for convenience or migrate tests to Symfony’s WebTestCase directly and retire the dependency.
• Maintenance prioritization: The deprecation is non-breaking today but creates future work. It should be scheduled as planned technical debt—ideally alongside the next PHP/Symfony upgrade—rather than deferred until removal.
• CI/CD and platform support: Dropping older PHP/Symfony versions affects the CI matrix and supported-platform matrix. This informs decisions about when to stop testing legacy combinations and when to communicate support changes to downstream teams.
• Feature and use-case fit: Best suited to PHP teams maintaining Symfony functional tests that need access to the dependency-injection container in test cases. It is not a Laravel testing package and should not be introduced into Laravel-only codebases.

When to Consider This Package

Consider it when:

• You maintain a Symfony application or bundle with functional tests that require container access.
• Your platform is already on PHP 8.1+ and Symfony 5.4+ (or you are planning that upgrade).
• You want a small, maintained helper that smooths container access in WebTestCase scenarios and are willing to absorb a deprecation cycle.
• You are standardizing test utilities across multiple Symfony services and want a shared functional-test base class.

Look elsewhere when:

• You are on PHP 8.0 or below, or Symfony 5.3 or below—1.5.0 no longer supports these.
• You are building on Laravel; Laravel’s native testing tools and Illuminate\Foundation\Testing\TestCase are the appropriate choice, not this Symfony-oriented package.
• You only need basic HTTP/functional assertions and can use Symfony’s native WebTestCase without an extra dependency.
• You require a package with no deprecations or a long-term support guarantee; the getDependencyInjectionContainer() deprecation indicates API churn is ongoing.

How to Pitch It (Stakeholders)

For executives: Release 1.5.0 is a maintenance release for a small Symfony test helper. It raises the minimum supported PHP and Symfony versions and deprecates one convenience method in favor of Symfony’s native container access. There is no immediate product impact, but it confirms our test tooling expects a modern PHP/Symfony baseline. The main decision is whether to align our upgrade timeline with this baseline or replace the package with native Symfony testing utilities.

For engineering: This release drops PHP <8.1 and Symfony <5.4, and deprecates WebTestCase::getDependencyInjectionContainer() in favor of getContainer(). Existing tests will continue to run on supported versions, but any call to the deprecated method should be migrated before removal. Treat this as scheduled maintenance: update the CI matrix, replace deprecated calls during the next test-suite touch, and reassess whether the wrapper still earns its place versus Symfony’s native WebTestCase.