In this article, I will describe all the steps I did to update from Symfony 5.2 to 5.4, together with all other packages I use. So these steps are closely linked to my software, but might also be helpful for others.
There are a lot of good articles on test driven development in php and some on doing this in Symfony. I use this a lot in my projects, including continuous integration via a Jenkins CI server. In this article, I will explain a few special things that I use in my tests, which might or might not be of help for others.
At some point, it is necessary to replace calls to an internal php function by a stub or mock which can be controlled by the test, e.g. to return certain error codes. Doing this will overwrite the php function for all tests that follow, so use it with care and only when all other options cannot be used. The following example shows how it is done, by replacing the php function file_get_contents.
I developed the first version of the software for a long time and ended up with Symfony version 2.8, after it was actively supported. I tried to migrate to symfony 3.4 using several of the migration guides available, but I failed. I could not get the system up and running again, because there are a lot of dependencies in the versions of the components, mixed with deprecations at a lot of places. To fix this, I started with a completely different approach: Start with a fresh up to date empty Symfony 4.3, and then migrate each file one by one. With this approach, I can also update each file and get the most benefit from new features, e.g. use the service injection / auto wiring also in non-service classes.
Passing a value to a form is a 3-step-process:
