Episode description
Episode description
In this episode, we revisit “How Google Tests Software,” published in 2012, to evaluate its relevance today.
We examine the roles of Software Engineers in Test (SETs) and Test Engineers (TEs), highlighting their responsibilities, tools, and the challenges they face. We explore the Test Certified system, a tiered framework that encourages developers to sharpen their testing skills. We also discuss Google’s test classifications—ranging from small to enormous—and the use of their internal bug database, Buginizer, to prioritize testing through risk-based assessments.
Discover how Google’s automated bots crawl millions of websites to evaluate web page appearances in Chrome. We also delve into their testing of Chrome OS and the continuous monitoring strategies employed for Gmail.
Finally, we spotlight Google’s method for gathering user feedback on Chrome bugs via the “Report an Issue” menu, which captures screenshots, OS information, browser details, and more.
More Resources: