How to do QA ✅ - by Luca Rossi and Jon Perl - Refactoring

Every week I get tons of questions from readers about topics I should cover in the newsletter. Some of the most frequent ones are about QA — in fact, I believe I receive at least one or two per week. Do people ask about niche optimizations or tactics? No, they ask about basic things: who should do QA, what good QA looks like, or whether you need QA at all. And you might think these come from fresh managers or young CTO founders — but no, they are often from folks who have 10+ years of experience, who are not afraid to admit they are just… confused. There is little consensus around the role of QA in modern engineering teams, which is why I am writing this piece today. I am not doing this alone: last week I interviewed Jon Perl, founder and CEO of QA Wolf, and we talked for one hour about all-things-QA. In this edition you will find the full video recording of the interview and my own write-up. The latter includes everything we covered in the chat, plus my own take and thoughts about it.

Every week I get tons of questions from readers about topics I should cover in the newsletter. Some of the most frequent ones are about QA — in fact, I believe I receive at least one or two per week. Do people ask about niche optimizations or tactics? No, they ask about basic things: who should do QA, what good QA looks like, or whether you need QA at all. And you might think these come from fresh managers or young CTO founders — but no, they are often from folks who have 10+ years of experience, who are not afraid to admit they are just… confused. There is little consensus around the role of