Legacy code and Test Driven Development (Part 2)

Yesterday, I wrote about legacy code and how it really was not possible to initially do test driven development, aka TDD. In this post, I will detail a strategy which I feel is good at explaining how to go about testing. I make no guarantees that this is the best way to go about it (please feel free to suggest other tricks you might use), but it works. But these are useful for me in porting Medusa V2 code to Medusa V4 (long story about why not V3, but there are reasons).

Legacy code and Test Driven Development

I am sure many of us have faced the task of trying to do test driven development (TDD) on a legacy codebase. I myself am facing such a challenge, with several tens of thousands of lines of code in a Laravel project which I am helping maintain and is around a decade old. And being severely behind in the packages it uses, the time has come to give the code some TLC, and update it to use the most recent versions of those package (for example, we are moving from Laravel 5 to 12).

Major Drupal upgrade and a new theme

I just spent the day (and then some) upgrading both the development version of this site and this site, and it has not been a fun upgrade. Part of the problem was that I had to switch themes, as the d8_blog_theme has apparently stopped being maintained. But thanks to my friend Dave, who does Drupal professionally, he cloned the repo and did some fixes in addition to making it compatible with Drupal 11.

Another WTF Chrome...

Why is it that periodically, I try to connect to my web server, which has a private IP address in my network, and I find that I have to go back into Chrome's settings, turn on secure DNS and turn it back off???  Grrr...