If you start by creating a bunch of simple test cases, you will probably run out of time before you create the powerful test cases. A large collection of simple, easy-to-pass test cases might look more rigorous than ad hod manual testing, but a competent manual tester is probably running increasingly complex tests as the program stabilizes.
如果你从创建一组简单的测试用例开始工作，那么你很可能在你创建强大的测试用例之前就把时间用光。一个大型、简单、且易于通过的测试用例集合会比专门的手动测试看起来更加严格，但是，一个有能力的手动测试者能在程序稳定的情况下运行日益复杂的测试。
12. Combining tests can find new bugs (the sum is greater than the parts). (Consensus)
联合测试能找出新的bug。(总和比各部分要强大) (一致同意)
13. There is value in using automated tests that are indeterminate (i.e. random) though we need methods to make a test case determinate. (Consensus)
虽然我们需要方法确定一个测试用例，但是使用不确定的(例如随机的)自动化测试也有价值。(一致同意)
We aren’t advocating blind testing. You need to know what test you’ve run. And sometimes you need to be able to specify exact inputs or sequences of inputs. But if you can determine whether or not the program is passing the tests that you’re running, there is a lot to be said for constantly giving it new test cases instead of reruns of old tests that it has passed.
我们并不鼓励盲目的测试。你需要知道你在运行什么测试。而且有时，你需要能指明准确的输入和输入序列。然而，如果你能确定程序是否通过了你在运行的测试，那将会不断带给它新的测试用例，而不是重新运行它已经通过的旧测试。
14. We need to plan for the ability to log what testing was done. (Consensus)
我们需要规划能记录已经完成的测试的功能。(一致同意)
Some tools make it easier to log the progress of testing, some make it harder. For debugging purposes and for tracing the progress of testing, you want to know at a glance what tests cases have been run and what the results were.
有些工具能容易地记录测试进程，而有些则很困难。对于调试目标和跟踪测试过程，你会想要大体知道已经运行了哪些测试用例，以及它们的结果是什么。
Staffing and Management
安排岗位和管理
15. Most of the benefit from automation work that is done during Release N (such as Release 3.0) is realized in Release N+1. There are exceptions to this truism, situations in which you can achieve near-term payback for the automation effort. Examples include smoke tests, some stress tests (some stress tests are impossible unless you automate), and configuration/compatibility tests. (Consensus)
从发行版N(比如发行版3.0)的自动化工作中得到的大部分收益往往在发行版N+1中才能实现。但也有例外，即你在某些情况下，可以获得自动化工作的近期回报。例如烟雾测试、一些强力测试(有些强力测试只有你使用自动化后才能实现)、以及配置/兼容性测试。(一致同意)
文章来源于领测软件测试网 https://www.ltesting.net/
