Listen "Why do you write your tests like that?"
Episode Synopsis
We discuss two "interesting" patterns we've observed in a number of Laravel projects. Let's take a step back and think about why we write tests the way we do.1:06 - One weird pattern we’ve seen in Laravel project tests2:23 - Can you explain why you’re doing this?3:50 - “It’s more readable”5:55 - Principle: learn a thing, do a thing, dissect a thing6:30 - Is it okay to have code duplication in tests?8:20 - How tests are different from application code11:16 - Don’t add application code just for your tests13:06 - Silly bitNeed help building a test suite for your Laravel app or making your existing tests more reliable? Click the link and book a free call to see how we can help.
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.