Google Test Certified Program: History, Levels, and Impact

The piece describes the origins of Google’s Test Certified (TC) program, launched in 2006 by Bharat Mediratta and Nick Lesiecki to promote automated testing awareness and improve code quality across engineering teams.

TC originally comprised three levels, each with specific tasks: Level One focused on establishing continuous build machines, test coverage metrics, and identifying fragile tests; Level Two introduced written policies prohibiting untested code submissions and refined test categorization; Level Three aimed for sustained, high‑coverage testing with low tolerance for failures. Later, fourth and fifth levels added stricter coverage goals and static analysis tools.

The certification process is informal: teams request a mentor, work with a volunteer familiar with the TC ladder, and after meeting perceived level requirements, undergo peer review to receive the appropriate certification.

To scale the program, Google leveraged its build system and dedicated tools, encouraging all engineering teams to climb the TC ladder, with test engineers (TEs) and senior engineers (SETs) acting as mentors and driving improvements.

Google added cultural elements—TC logos on T‑shirts, coffee mugs, and contests rewarding teams with points and prizes—to make participation engaging.

The article concludes with a balanced assessment: TC exceeded expectations by fostering widespread discussion, tool development, and higher testing standards, though it also sparked debates over metrics and bureaucracy. Overall, the grassroots initiative contributed to a lasting culture of high‑maintainability code at Google.