phpunit-injector VS php-ddd-example

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:

Have a look at https://symfonycasts.com/screencast/symfonycon2019/hexagonal-architecture-with-symfony (and all resources from Matthias Noback including books, tweets and blogposts). Also check: - https://github.com/CodelyTV/php-ddd-example - https://github.com/msgphp/msgphp - https://minompi.medium.com/symfony-and-hexagonal-architecture-b3c4704e94de- https://blog.elao.com/fr/dev/architecture-hexagonale-symfony/ (needs to be translated from french, but really good one). - https://verraes.net/ (and all resources/tweets/blogposts from Mathias Verraes who has really good knowledge on DDD topics)