Google Testing Blog
Google's long-running blog on testing and code quality, including well-known posts on flaky tests, test sizes, end-to-end testing trade-offs and the one-page "Testing on the Toilet" tips. Good reading once you automate, for the reasoning behind maintainable suites at very large scale.
Guide
Other
Intermediate
Free
What it is
The Google Testing Blog is Google's public blog about software testing and code quality, written by engineers across the company. It has been running for many years and has a deep archive of posts on testing practice, test infrastructure and the culture that supports them.
What you will find
- Flaky tests: posts such as "Flaky Tests at Google and How We Mitigate Them" explain how often tests are flaky at scale, what causes it and how teams handle it.
- Test design and trade-offs: posts on test sizes, the costs of end-to-end tests compared with smaller tests, and how to keep suites fast.
- Testing on the Toilet: short, practical tips originally printed for Google's offices, each on one idea such as naming tests, avoiding logic in tests or choosing test doubles.
- Code quality and review: writing testable code, readability and code review practice.
Is it worth your time?
Once you are automating, yes, in small doses. It is not a course and not tool documentation; most posts explain why rather than how, with examples drawn from a very large codebase. That reasoning is exactly what helps you make good decisions about your own suite: what to test at which level, how to spot and kill flakiness, and how to write tests others can maintain. The Testing on the Toilet posts are short enough to read one a day.
Things to keep in mind
Some advice assumes Google's scale and infrastructure, which your team will not have. Take the principles and adapt the practice. Older posts may mention tools that have changed; the ideas usually hold.
Prerequisites
Some experience writing automated tests, so the problems described are familiar.
Free or paid?
Free.
How to use it
Start with the flaky tests post and a handful of Testing on the Toilet entries, then search the archive when you face a specific question, such as test doubles, test data or end-to-end test strategy. Pair it with the free Software Engineering at Google book, whose testing chapters expand on many of the same ideas.
Common questions
Is it only relevant to big companies? No. Flakiness, slow suites and hard-to-read tests happen in teams of any size, and the principles apply.
Ready to start?
Opens on Google in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.