时间不够时应该怎么测试？testing under less time constraint?

出处：http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/
自己瞎翻译的=。=|

Sometimes Tester need common sense to test a application!!!
有些时候，测试人员需要一些共识去测试一个应用程序！！！

I am saying this because most of the times it is not possible to test the whole application within the specified time. In such situations it’s better to find out the risk factors in the projects and concentrate on them.
这样做的原因是：很多时候，根本没有足够的时间去测试整个应用程序。在这样的情况下，最好的做法就是找出项目中的风险因素并且将工作重点集中在这些风险因素上。

Here are some points to be considered when you are in such a situation:
当你处于这种情况下，你是否考虑过以下的建议？

1. Find out Important functionality is your project?
   是否找出了项目中最重要的功能？
2. Find out High-risk module of the project?
   是否找出了项目中风险最高的功能模块？
3. Which functionality is most visible to the user?
   哪个功能是用户最常用的？
4. Which functionality has the largest safety impact?
   哪个功能对安全性影响最大？
5. Which functionality has the largest financial impact on users?
   哪个功能对用户充值影响最大？
6. Which aspects of the application are most important to the customer?
   应用程序哪个方面是对用户最重要的？
7. Which parts of the code are most complex, and thus most subject to errors?
   哪部分代码最复杂（或者说其它功能关联最多）？这是最容易出错的吗？
8. Which parts of the application were developed in rush or panic mode?
   哪部分功能是赶工或者在混乱的模式下开发的？
9. What do the developers think are the highest-risk aspects of the application?
   程序的哪方面是开发人员认为高风险的？
10. What kinds of problems would cause the worst publicity?
    哪些问题会导致最坏的程序评论（口碑）？
11. What kinds of problems would cause the most customer service complaints?
    哪些问题最有可能导致客户投诉？
12. What kinds of tests could easily cover multiple functionalities?
    哪些测试会很轻松的覆盖多个功能？

Considering these points you can greatly reduce the risk of project releasing under less time constraint.
在测试完全不够的时候，考虑这些建议，你将会极大的减少项目发布版本的风险。