I’ve written about test strategy, QA team structure, studio culture, and live support for Game Developer (formerly Gamasutra). The ideas in these pieces are the ones I still build teams around.
Combining QA, customer care, and community into one Live Support team, meeting players where they already talk, and cutting critical fixes from months to days.
Functional testing still matters, and quality is everyone’s job. A risk-based workflow that combines automation with hands-on testing across the full development lifecycle.
Embedding testers on feature teams isn’t enough by itself. A center of excellence plus integrated teams of engineers in test, software engineers, and testers makes QA sustainable under Agile.
Quality can’t be tested into a game at the end of the pipeline. Why test belongs inside development, and how that turns QA from a gate into a source of risk information.