Coding on the weekends:
(It's Memorial Day in the US, so today still counts as weekend.)
I have a `schema(): string` method. It returns JSON. Writing tests (because I'm a TDD person). I've come across a thing with #PHPUnit that surprised me a little.
There is no assertion for `assertJsonStringContainsJsonString()`. So I am making do with `assertStringContainsString()` where I want to test parts of the JSON without having to deal with the entire thing.
Is there a better way?
I have learnt more from the failures of PHPUnit than its successes. Over the last 25 years, I have witnessed the evolution of testing philosophy from a marginal practice to the bedrock of modern software development. But has the PHP community learned the right lessons?
In this presentation, I share what I have learned from #PHPUnit, how my approach has evolved (sometimes unexpectedly), and my thoughts on the future of software development in the age of AI:

Every two months, alongside each #PHPUnit feature release, I send subscribers a detailed walkthrough of the new features: what they do, how they are implemented, and why they were added. It's the context the ChangeLog doesn't cover.
PHPUnit 13.2 is less than two weeks away: high time for me to start working on the next issue of my newsletter. And high time for you to subscribe, if you have not done so already:
HTTP requests using drupalGet() While in general, Functional tests are designed for the testing of page loads, it's possible to test these in Kernel tests too. The advantage is that Kernel tests are much faster to run, because they only set up what they need to. The faster running time is particularly useful if many different combinations need to be tested for. The trade-off is that some aspects of the Drupal site are not available, such as form submissions and session handling, and that more set-up is required (but you only set up the elements the test needs).