A test that saves object numbers tests PHP, not your code
Miguel Sampedro added one line to a Symfony AI pull request and 25 tests failed, although not a single assertion had changed. The cause was in the saved expected results: they contained the internal numbers PHP gives to objects while it runs. Add one object and every number after it shifts, so every comparison breaks. Those tests were checking something nobody ever meant to check, the order in which PHP creates things. The fix was to stop saving those numbers. What I take from it: a test should only remember what I would defend in a review. Anything the machine makes up on its own is noise, and sooner or later it makes a harmless change look like a bug.
// MORE SHORTS
Adding AI to a project is mostly dependency work →
Live on Never Code Alone we set up Sulu AI Intelligent Search. The feature itself took a few commands. The rest was the project around it.
// MORE SHORTS
Who Symfony's new bundles are actually for →
Symfony 8.2 is moving configuration out of FrameworkBundle and into 29 bundles shipped by the components that actually own it: Messenger, HttpClient, Cache, Scheduler, PropertyInfo and many others.