Test Common Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for test infrastructure — resolved toward "build." elcodi/test-common-bundle is a shared test-utility bundle (base test cases, fixtures, and mocks reused across Elcodi's e-commerce bundles). Its existence confirms the pattern is worth having in a Symfony codebase, but the artifact itself is not a viable dependency. The decision it informs is: we write our own ~200-line internal test-support package, not adopt this one.
• Roadmap scoping for a test-tooling initiative. Use this as a reference of scope, not code: what belongs in a shared test kit (abstract WebTestCase-style base classes, fixture loaders, service-container mocks). Treat it as a checklist for our own package's surface area.
• Dependency-risk review / supply-chain policy input. A read-only subtree split with 0 stars, 0 dependents, last release 2014-08-14, and a stated policy of not accepting PRs is a textbook example of a dependency that will never receive a security or compatibility patch. This supports a policy decision to require active maintenance or vendoring for any PHP dependency.
• Legacy migration triage. If any team inherits an Elcodi-based shop, this identifies the package as part of the abandoned upstream suite — supports a "plan exit" rather than "plan upgrade" decision on that codebase.
• Not a differentiator. Opportunity score of 22.97 places it in the "no product leverage" band; nothing here touches customer-facing capability, pricing, or time-to-market in a way worth roadmap time.

When to Consider This Package

• Essentially never for new work. Criteria that would normally justify adoption — active releases, meaningful dependent count, maintained issue tracker, modern PHP/Symfony constraint support — all fail.
• Viable only as a read-only reference. Acceptable use is reading the source to understand how Elcodi structured shared test helpers before we design our own. Do not composer require it.
• Only if you are already pinned to the Elcodi ecosystem. If a legacy application already depends on elcodi/elcodi and the transitive graph, adding its own subtree split is at least internally consistent — but the correct move there is to freeze and migrate, not to expand usage.
• Look elsewhere (or build) when:
  • You are on PHP 8.x and Symfony 6/7 — this predates both; expect PHPUnit 4-era APIs, deprecated Symfony test base classes, and hard incompatibilities.
  • You need maintained fixtures/DI test tooling — use Symfony's own symfony/framework-bundle test utilities, doctrine/data-fixtures, alice/nelmio/alice for fixtures, and Mockery/PHPUnit mocks directly.
  • Your organization requires a security-response path — the read-only policy explicitly forecloses one.
  • You need support — the documented channels point to an inactive Gitter room, a docs site, and Twitter handles from the mid-2010s.

How to Pitch It (Stakeholders)

For executives: We evaluated a small open-source PHP test-support library for reuse in our Symfony test suite. It is part of the Elcodi e-commerce suite, which has been unmaintained since roughly 2014 — zero GitHub stars, zero downstream dependents, and a published policy of not accepting fixes. Adopting it would import technical debt and an unfixable security surface for a benefit we can replicate in a few days of engineering. Recommendation: no adoption; build a small internal test-support package instead. Cost is modest and one-time; risk avoidance is permanent.

For engineering: Treat this as a documented "do not use." It is a read-only subtree split of elcodi/elcodi, MIT-licensed, last tagged August 2014, targeting a Symfony 2-era stack. Its value is purely as a design reference for what a shared test kit should contain (base test cases, fixture utilities, container mocks). We will implement equivalent helpers against our current Symfony and PHPUnit versions, keep them in a first-party package, and pin them to our own release cadence — which is the only way we get compatibility patches. Flag any transitive appearance of Elcodi packages in a legacy audit as a migration item, not a maintenance item.