测试时如何安排各个模块的测试优先顺序

注意！！以下文字摘抄自《软件测试的经验与教训》。
迅速找出重要程序问题
    测试员的使命很可能包括找出重要的（与无意义相反）程序问题，而且要迅速找出。如果是这样，那么这对测试员所执行的测试意味着什么呢？

• ·首先测试经过变更的部分，然后测试没有变化的部分。修改和更新都意味着新的风险。
• ·首先测试核心功能，然后测试辅助功能，测试产品所完成的关键和常用功能，测试完成产品基本任务的功能
• ·首先测试能力，然后测试可靠性。先测试每个功能是否完全能用，然后再深入检查任何一个功能在很多不同条件下的表现如何
• ·首先测试常见情况，然后测试少见情况。使用常用的数据和使用场景。
• ·首先测试常见威胁，然后测试罕见威胁。用最有可能出现的压力和错误情况进行测试。
• ·首先测试影响大的问题，然后测试影响小的问题。测试在出现失效的情况下会产生大量破坏的产品部件。
• ·首先测试最需要的部分，然后测试没有要求的部分。测试对团队其他人有重要意义的任何部分的任何问题。

    测试员如果对产品。产品必须与之交互的软件和硬件以及将使用软件的人越了解，越有可能更快地找出重要问题。应好好研究这些方面的内容。

英文版本
Lesson 5:Find important bugs fast

    Most likely,your mission includes finding bugs that are important (as opposed to insignificant) and finding them quickly. If so ,what does this mean in terms of the tests you run?

• Test things that are changed before things that are the same.Fixed and updates mean fresh risk.
• Test core functions before contributing functions.Test the critical and the popularthings that the product does.Test the functions that make the product what it is.
• Test capability before reliability.Test whether each function can work at all before going deep into the examination of how any one function performs under many different conditions.
• Test common situations before esoteric situations.Use popular data and scenarios of use.
• Test common threats before exotic threats.Test with the most likely stress and error situations.
• Test for high-impact problems before low-impact problems.Test the parts of the product that woulddo a lot of damage in case of failure.
• Test the most wanted areas before areas not requested.Test an areas and for any problems that are of special interest to someone else on the team.

    You will also find important problems sooner if you know more about the products,the software and hardware it must interact with, and the people who will use it.Study these well.