Cristian Medina wrote an article recently called "Test Engineering Anti-Patterns: Destroy Your Customer Satisfaction and Crater Your Quality By Using These 9 Easy Organizational Practices"Of course, it's sarcastic, and aims to highlight many problems with organizational practices that reduce software quality.The article doesn't go out of character, and only promotes the anti-patterns. However, in this interview, we discuss each point, and the corollary of what you really should do. At least, our perspectives.Here's the list of all the points discussed in the article and in this episode:Make the Test teams solely responsible for qualityRequire all tests to be automated before releasingRequire 100% code coverageIsolate the Test organization from DevelopmentMeasure the success of the process, not the product. Metrics, if rewarded, will always be gamed.Require granular projections from engineersReward quick patching instead of solvingPlan for today instead of tomorrowSpecial Guest: Cristian Medina.Links:Test Engineering Anti-Patterns: Destroy Your Customer Satisfaction and Crater Your Quality By Using These 9 Easy Organizational Practices — The article we discuss in the show.tryexceptpass — Cris's blog

Ver todos los episodios