Google Test Certified Program: History, Levels, and Certification Process

Google launched the Test Certified (TC) program in early 2006 to encourage engineers to adopt automated testing practices, improve code quality, and increase test coverage across the company.

TC consists of multiple certification levels—originally three, later expanded to five—each with specific tasks such as establishing continuous build machines, defining test size categories, creating written testing policies, and achieving higher coverage goals.

The certification process is informal: a team selects a mentor, adopts TC tools and metrics, and after mutual agreement on meeting level requirements, the mentor conducts a review and grants the appropriate certification based on peer evaluation.

To scale the program, Google leveraged its build system and dedicated volunteers (Test Engineering/EP teams) to promote TC adoption, integrate it into team goals, and provide incentives like T‑shirts, mugs, and contests.

While TC has driven widespread discussion on testing standards, tool development, and cultural change—leading many teams to improve their testing habits—it also faced resistance from engineers questioning its value and measurement criteria.

Overall, the Test Certified initiative exceeded its original expectations, becoming a de‑facto engineering standard at Google, fostering higher code maintainability, and illustrating how a bottom‑up effort can achieve lasting impact on software quality practices.