4. Testing is done through an external interface ("black box testing"). The same analysis applies to testing at the code level - and a brief example is given toward the end of the paper - but I will not describe all the details.
5. There is no mandate to automate. Management accepts the notion that some of your tests will be automated and some will be manual.
6. You first design the test and then decide whether it should be automated. In reality,it’s common for the needs of automation to influence the design. Sadly, that sometimes means tests are weakened to make them automatable. But if you understand where the true value of automation lies - it can also mean harmless adjustments or even improvements.
7. You have a certain amount of time to finish your testing. You should do the best testing possible in that time. The argument also applies in the less common situation of deciding on the tests first, then on how much time is required.作者: migen 时间: 2006-2-9 11:43 标题: 自动化测试的时间 4. 测试通常通过一个外部界面("黑盒子测试")来完成 。 同样的分析适用于测试在编码级段，并且一个简要实例将在本文的末端给出， 但我不会描述所有细节。
5. 没有人命令必须自动化测试。管理者一般赞同的做法是部分自动化测试,部分手工测试。
6. 您首先得设计测试用例，然后再决定是否应该被自动化执行。在实际上,自动化测试的需求通常影响着测试计划。 令人遗憾的是, 有时候测试案例方法使他们自动测试的意义不大 。 但如果您了解自动化测试谎言的真实价值在何处- 它也意味着无害的调整甚至改善。
7. 您有一固定时间完成测试任务。 您应该在这段时间做最可能多的测试。 这一观点的应用就在于首先测试时间需求短的案例，然后再测试时间需求比较长的案例。