✳flâneur — a map of the web's best reading

Google Testing Blog

testing.googleblog.com · 1,200 words · saved by 1 readers

The test pyramid is the canonical heuristic for guiding test suite evolution. It conveys a simple message - prefer more unit tests than integration tests, and prefer more integration tests than end-to-end tests. While useful, the test pyramid lacks the details you need as your test suite grows and you face challenging trade-offs. To scale your test suite, go beyond the test pyramid. The SMURF mnemonic is an easy way to remember the tradeoffs to consider when balancing your test suite: Speed: Unit tests are faster than other test types and can be run more often—you’ll catch problems sooner. Maintainability: The aggregated cost of debugging and maintaining tests (of all types) adds up quickly. A larger system under test has more code, and thus greater exposure to dependency churn and requirement drift which, in turn, creates more maintenance work. Utilization: Tests that use fewer resources (memory, disk, CPU) cost less to run. A good test suite optimizes resource utilization so that it

Google Testing Blog Testing Blog Prefactoring: Clear the Way for Your New Feature Tuesday, July 21, 2026  No comments Google Labels: Rahul Singal , TotT Choosing Values for Robust Tests Thursday, June 04, 2026  No comments Google Labels: Radion Khait , TotT Code Review Responses: Add Context When It Counts Tuesday, May 12, 2026  No comments Google Labels: Saicharan Nimmala , TotT Construct with Collaborators, Call with Work Tuesday, May 05, 2026  No comments Google Labels: Shahar Roth , TotT One Map Key, One Lookup Wednesday, April 29, 2026  No comments

Explore this link on the map →

related reading