谷歌软件测试之道
How Google Tests Software
James A. Whittaker · 初版 2012 年
3人推荐
6位读者提及
8次提及
数以亿计的代码行分布在数十亿个源文件中。每天数十亿次构建操作触发数百万次自动化测试。每天数十万个浏览器实例运行。应用程序以持续不断的节奏发布。女士们先生们，没有比这更棘手的挑战了（至少相差无几）。关于作者：James是Google的工程总监，曾负责Chrome、地图以及Google网页应用的测试。他曾就职于Microsoft，此前还当过教授。James是测试领域最知名的人物之一。Jason是测试工程师
Hacker News 上怎么说
正在加载完整评论……
可能反直觉的是，大多数科技巨头并没有专门的 QA 和测试人员岗位，相反，他们鼓励工程师在开发产品的同时去思考软件质量。参考《How Google tests software》这本书（James A. Whittaker 著，2012 年），Pragmatic Engineer 博客上也有一篇很棒的文章讲述大厂是如何做 QA 的：https://newsletter.pragmaticengineer.com/p/qa-across-tech
Maybe counterintuitively, most big tech companies have no dedicated QA & tester roles, rather, they encourage engineers to think about software quality while developing product. See the book "How Google tests software" (by James A. Whittaker, 2012) and the Pragmatic Engineer blog has a good post on how big tech does QA: https://newsletter.pragmaticengineer.com/p/qa-across-tech
……极速响应的产品（Superhuman）、傻瓜式简易上手（Stripe）、信息图表与可落地的数据（FiveThirtyEight）、分布式协同开发与 CI（Github）、硬核的测试水平（《How Google Tests Software》），以及打造我们梦寐以求的公司文化。该岗位纯线下办公，地点位于洛杉矶市中心。感兴趣请发送邮件至 hello (at) audacious (dot) io
…blazingly-fast products (Superhuman), stupid simple on-boarding (Stripe), infographics and actionable data (FiveThirtyEight), distributed collaborative development and CI (Github), testing bad-ass-ery ("How Google Tests Software"), and building the company culture we dream about. This role is exclusively onsite in Downtown Los Angeles. If you are interested please email hello (at) audacious (dot) io
……极速响应的产品（Superhuman）、傻瓜式简易上手（Stripe）、信息图表与可落地的数据（FiveThirtyEight）、分布式协同开发与 CI（Github）、硬核的测试水平（《How Google Tests Software》），以及打造我们梦寐以求的公司文化。该岗位纯线下办公，地点位于洛杉矶市中心。感兴趣请发送邮件至 hello (at) audacious (dot) io
…blazingly-fast products (Superhuman), stupid simple on-boarding (Stripe), infographics and actionable data (FiveThirtyEight), distributed collaborative development and CI (Github), testing bad-ass-ery ("How Google Tests Software"), and building the company culture we dream about. This role is exclusively onsite in Downtown Los Angeles. If you are interested please email hello (at) audacious (dot) io
……针对何时需要手动测试、测试量多大以及手动测试究竟该涵盖哪些内容制定一套规范，起到了极其巨大的帮助。在《How google tests software》这本书里讲得相当清楚。有了相关规范，就意味着不会在什么该由谁自动化、剩下什么留给谁去探索性测试等问题上产生误解。
…and it's been incredibly helpful to create a policy around when something requires manual testing, how much and what the manual testing should actually cover. It's covered reasonably well in the book "How google tests software". Having a policy around that means that there's no misunderstanding what gets automated and by whom, and what's left for exploring and by whom.
Google 搜了一下没找到太多。我只知道这几本：Douglas Edwards 写的《I'm Feeling Lucky: The Confessions of Google Employee Number 59》、James A. Whittaker 写的《How Google Tests Software》。还有别的吗？补充说明：我指的是曾在 Google 任职的前员工，或者现在还在 Google 工作的人写的。
A Google search didn't return much. These are the ones which I know of: "I'm Feeling Lucky: The Confessions of Google Employee Number 59" by Douglas Edwards "How Google Tests Software" by James A. Whittaker Any others? Edit: Clarification: I meant those who were Google employees at some point as well as those who are working at Google now.
对《How Google Tests Software》（https://www.amazon.com/Google-Tests-Software-James-Whittaker...）这本书的这篇书评（https://www.amazon.com/gp/customer-reviews/RGB0DI8V7KLN1/?AS...）给出了一些线索。我自己没有买这本书，是不久前在一个 QA 工程师的桌上看到的。
This review https://www.amazon.com/gp/customer-reviews/RGB0DI8V7KLN1/?AS... of the book "How Google Tests Software" (https://www.amazon.com/Google-Tests-Software-James-Whittaker...) gives a couple of hints. I don't own the book myself, I saw it on the desk of a QA engineer a while back.