基于风险的测试考虑：
从项目管理的角度去考虑基于风险的软件测试
如项目的决策，资金，人员，环境等等角度。（文章中谈到的应该是站在测试员的角度从这些方面考虑带来软件缺陷的可能，但我个人认为似乎我们还应该站在项目的角度去看整个项目的成败，决策的正确，管理的合理。也许还应该站在项目经理的角度去看待测试。）
从用户的角度去看待测试工作。
什么用户类型；用户使用可能性；尽量缩小测试范围。
从产品本身去考虑：
缺陷模式：软件缺陷应该从三个角度考虑：
1. 产品因素：产品都有什么构成？对于每个组成部分，产品是怎么可能发生缺陷？
2. 质量因素：易用性，可用性，可维护性。
3. 一般的编程错误
How a software tester thinking?
I summarized some good tips from that document below:
Tips1:
Instead of this… | consider this |
–complete specs | –implicit specs & inference（隐含的规格和推论） |
– quantifiable criteria | –meaningful criteria（有意义的标准） |
– protected schedule | –risk-driven iterations（风险带来的反复） |
– early involvement | –good working relationship（良好的工作关系） |
– zero defect philosophy | –good enough quality（足够好的质量） |
– complete test coverage | –enough information（足够的信息） |
简而言之：作为一个软件测试员，不要只是做好测试工作，而是以整个产品的质量为出发点去考虑，以整个组织、整个项目为出发点去考虑做好测试工作。（Summarized that a tester shouldn’t do test work just think as how to do test the product, but a tester should think broadly as how to do the good job as a member in organization, how to do can contribute for all project success）.
Tips2:
Thinking about Coverage
Testers with less expertise…
– Think about coverage mostly in terms of what they can see.
– Cover the product indiscriminately.
– Avoid questions about the completeness of their testing.
– Can’t reason about how much testing is enough.
Better testers are more likely to…
– Think about coverage in many dimensions.
– Maximize diversity of tests while focusing on areas of risk.
– Invite questions about the completeness of their testing.
– Lead discussions on what testing is needed.
一个好的测试人员知道什么方面的测试是重要的，什么是次要的。知道测试到什么地步是适可而止的。
Tips3:
HICCUPP
Consistent withHistory: Present function behavīor is consistent with past
behavīor.（与以前版本产品的对比）
Consistent with ourImage: Function behavīor is consistent with an image that
the organization wants to project.（与组织预期的期望相一致）
Consistent withComparable Products: Function behavīor is consistent with
that of similar functions in comparable products.（与同类产品对比一致）
Consistent withClaims: Function behavīor is consistent with what people say it’s
supposed to be.（与周围人们的看法一致）
Consistent withUser’s Expectations: Function behavīor is consistent with
what we think users want.（与用户的期望一致）
Consistent withinProduct: Function behavīor is consistent with behavīor of
comparable functions or functional patterns within the product.（与产品内部的一致）
Consistent withPurpose: Function behavīor is consistent with apparent purpose.
（与项目的目的一致）
