Google’s Test Certified Program: History, Levels, and Impact on Automated Testing

In 2010 Google’s automated testing landscape looked enviable, whereas in 2005 engineers struggled with endless quality issues, heavy manual testing workloads, and a testing department seen merely as a service unit.

To address this, Google engineers formed a dedicated group in 2006 and introduced the Test Certified (TC) program, a voluntary certification framework with three primary levels (later expanded to five) designed to raise awareness of code quality and automate testing coverage.

TC’s three original levels each define specific goals: Level One focuses on establishing continuous integration, coverage metrics, and test categorization; Level Two adds written testing policies, prohibiting untested code submissions, and refining test size classifications; Level Three aims for sustained, high‑coverage testing with low tolerance for flaky tests.

The certification process is informal: teams request a mentor, work with a volunteer guide to adopt tools and standards, and upon mutual agreement undergo a peer review to receive the appropriate TC level.

Scaling the program relied on Google’s build system and the involvement of Test Engineering (TE) and Software Engineering Tools (SET) teams, turning TC into a company‑wide driver for improving testing practices and reducing low‑level defects.

To keep the initiative engaging, Google created TC branding, merchandise, and challenges that rewarded teams with points, prizes, and recognition, fostering a fun, competitive environment.

The program’s outcomes include widespread adoption across many projects, heightened discussion around testing processes, and a lasting cultural shift toward higher code health, despite occasional debates over metrics and bureaucracy.

Overall, Test Certified demonstrates how a grassroots, bottom‑up effort can achieve significant, durable improvements in automated testing and engineering quality within a large organization.