软件测试的艺术
The art of software testing
Glenford J. Myers · 初版 1979 年
6人推荐
11位读者提及
14次提及
为什么值得读
- 颠覆性指出成功的测试是发现缺陷而非证明无错
- 提供不依赖特定编程语言的走查与测试清单
- 篇幅约百页短小精炼，开篇的经典案例发人深省
Hacker News 上怎么说
正在加载完整评论……
The art of software testing
Glenford J. Myers · 初版 1979 年
正在加载完整评论……
格伦福德·迈尔斯（Glenford Myers）的《软件测试的艺术》（The Art of Software Testing）里有一份非常优秀的、与具体语言无关的 check list。可以看看关于“walkthroughs”那一章。
The Art of Software Testing by Glenford Myers has an excellent language-agnostic checklist. See the chapter on “walkthroughs”
……设计长期架构。极棒的茶几读物：爱德华·塔夫特的《构想信息》（Envisioning Information）；尼尔·加布勒的《华特·迪士尼》（Walt Disney），或许是有史以来最伟大 imagineer 的绝佳传记；格伦福德·J·迈尔斯的《软件测试的艺术》（The Art of Software Testing），一本 100 页左右的经典之作。核心前提是：成功的测试是能够发现 bug/问题的测试，而不是找不到问题的测试。
…designing long-term architectures. Excellent coffee table book "Envisioning Information" by Edward Tufte "Walt Disney" by Neal Gabler Excellent biography of maybe the greatest imagineer ever "The Art of Software Testing" by Glenford J. Myers ~100 page classic. The central premise is that the successful test is one that finds bugs/issues not one that doesn't.
格伦福德·迈尔斯写的《软件测试的艺术》（The Art of Software Testing）很棒。https://en.wikipedia.org/wiki/Glenford_Myers [1] 书开头的那段轶事，他抛出了一个简单的问题——你能为此写出多少个 test case……
The Art of Software Testing by Glenford Myers is great. https://en.wikipedia.org/wiki/Glenford_Myers [1] The anecdote in the beginning of the book, where he poses a simple question - how many test cases can you write for this…
想要了解一些关于编写测试的经典智慧，可以看看格伦福德·迈尔斯写的经典《软件测试的艺术》（The Art of Software Testing）。在亚马逊上要卖 149 美元以上，但在 eBay 上只要 5 美元：https://www.ebay.com/sch/i.html?_from=R40&_trksid=p3671980.m... 这本书最初出版时 TDD 还没影儿呢，但实用性极强。
For some classic wisdom about writing tests see the classic "Art of Software Testing" by Glenford Myers. It's $149+++ on Amazon, but only $5 on ebay: https://www.ebay.com/sch/i.html?_from=R40&_trksid=p3671980.m... This was originally published before TDD was a thing, but is highly applicable.
我觉得《软件测试的艺术》（The Art of Software Testing）是这个领域一本很好的指南。推荐一读。
I found Art of Software testing to be a good guide on the subject. I recommend reading it.
一般来说，你可以通过因果图法（cause effect graphing，出自《软件测试的艺术》）等技术来减少测试中的组合数。它还包含表示“不可能发生”（can't happen）情况的符号标记。这本书偏重技术细节，所以我不确定它能不能解决你的问题。
Generally speaking, you can reduce the combinatorics in tests by using techniques like cause effect graphing (from The Art of Software Testing). It also contains notation for cases that "can't happen". It's very technical so I'm not sure if it will solve your problem.