Listen "Should you change application code to support a test?"
Episode Synopsis
When you're writing a test it can be so tempting to just "tweak" some app code to make it easier to write that test, but we discuss why that might not be a good idea. We also talk about some app changes while writing tests that are beneficial to the overall project.(00:00) - Sometimes changing code makes testing easier
(01:30) - Different types of code changes
(02:45) - An example with Laravel jobs
(04:30) - A time when it's okay to change code while testing
(08:50) - Avoid problems by writing tests earlier
(09:30) - Silly bit
Don't "compromise" on testing. See how we can help level up your Laravel project.
More episodes of the podcast No Compromises
Why I changed my mind about down migrations
03/01/2026
Why senior developers feel wrong more often
20/12/2025
Should you ever hand-format code?
06/12/2025
Discussing different ways to model data
22/11/2025
Read outside tech to expand your horizons
08/11/2025
Should you use DTOs in Laravel?
27/09/2025
Sunsetting a company app without loose ends
13/09/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.