Ten years ago today, the first Google Testing Blog article was posted (official announcement 2 days later). Over the years, Google engineers have used this blog to help advance the test engineering discipline. We have shared information about our testing technologies, strategies, and theories; discussed what code quality really means; described how our teams are organized for optimal productivity; announced new tooling; and invited readers to speak at and attend the annual Google Test Automation Conference.

Google Testing Blog banner in 2007

The blog has enjoyed excellent readership. There have been over 10 million page views of the blog since it was created, and there are currently about 100 to 200 thousand views per month.

This blog is made possible by many Google engineers who have volunteered time to author and review content on a regular basis in the interest of sharing. Thank you to all the contributors and our readers!

Please leave a comment if you have a story to share about how this blog has helped you.

Hi, I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. In addition, several articles have been a big source of inspiration for company-wide standards and guidelines with respect to software testing.Thanks for the great blog!

Hey all I just wanted to say thanks! I have been a reader for several years. Now I write a blog series about Android testing and I often refer to this blog as a primary resource then write about how the concepts apply to Android like in this post https://medium.com/android-testing-daily/testing-state-vs-testing-interaction-c5d7fe0bf247#.8a6a4ez1x. Keep up the good work!

Back in 2009 I started reading Misko Hevery's articles about designing for testability and Dependency Injection. I have witnessed the transformation of the PHP community from procedural code to true object-orientation, also thanks to these patterns which are now pushed by every decent framework.

Happy Birthday! I firstly read the new explanation of test engineer role is here! Although I don't comment much here, but I hope this test blog is always the best place we can learn and share new idea of testing.

Hey all I just wanted to say thanks! I have been a reader for several years. I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. Test technologies and codeless testing

I'm late to wish you a happy birthday. I have enjoyed this and many other Google tech blogs

I found you today because I wanted to get some understanding of code coverage analysis on large-scale projects. We have a pretty big codebase (>5M C# loc) and a big investment in integration testing (goes to the database). Our testing is costly and hard to measure coverage with standard tools, so we built our own. It was useful to read about how you do it. I'm glad I found that you measure median rather than mean coverage.

And next I found your front-page article is about flaky tests. We have a bunch of those too. We don't have any predictor for them, but our application is in the financial sector and we have some tests that fail on a certain day of the month or week.