Symfony DI VS phpunit-injector

Compare Symfony DI vs phpunit-injector and see what are their differences.

Symfony DI

Allows you to standardize and centralize the way objects are constructed in your application (by symfony)

phpunit-injector

Injects services from a PSR-11 dependency injection container to PHPUnit test cases (by jakzal)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Symfony DI phpunit-injector
0 1
4,049 61
0.4% -
8.3 4.0
11 days ago 3 months ago
PHP PHP
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Symfony DI

Posts with mentions or reviews of Symfony DI. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Symfony DI yet.
Tracking mentions began in Dec 2020.

phpunit-injector

Posts with mentions or reviews of phpunit-injector. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-04.
  • Testing with immutable PSR-7 objects and Prophecy
    3 projects | dev.to | 4 Mar 2021
    This unit test will fail when ran against the implementation from earlier. And in this situation a failing test is a good thing. But for this specific situation another "issue" has made it's way into the testcase; the unit test is now depending on the implementation that is being used for PSR-7. When working in a large codebase - like I currently am - one might have more than just a few usages of these interfaces and thus unit tests. Using the suggested approach, instantiating value objects instead of prophesizing, will lead to a large amount of object instantiations. And this will make switching to another implementation more work. Ideally this instantiating is centralized as much as possible. This is exactly why PSR-17 - HTTP Factories - was introduced. Typically dependencies - like these factories - are injected. For unit tests this is not feasible without plugins. My solution is a bit less fancy; a trait:

What are some alternatives?

When comparing Symfony DI and phpunit-injector you can also consider the following projects:

PHP-DI - The dependency injection container for humans

Pimple - A small PHP dependency injection container

Nette DI - 💎 Flexible, compiled and full-featured Dependency Injection Container with perfectly usable autowiring and support for all new PHP 7 features.

Auryn - IoC Dependency Injector

Container - Small but powerful dependency injection container

zend-servicemanager

ClanCats Container - 🚀 PHP Service Container with fast and cachable dependency injection.

doctrine-test-bundle - Symfony bundle to isolate your app's doctrine database tests and improve the test performance

Acclimate - Adapters for PHP framework containers to an interoperable interface

Disco - PSR-11 compatible Dependency Injection Container for PHP.

php-ddd-example - 🐘🎯 Hexagonal Architecture + DDD + CQRS in PHP using Symfony 6

php-dependency-injection - PHP Dependency Injection Container PSR-11