典型的测试错误有哪些？(9)

　　但是不利之处超过了有利之处：新雇员迫不及待地要离开测试行业。这很难产生高质量的工作。你可能会争辩说测试员为了“被释放”，必定会好好工作。不幸的是，过程给人留下的印象常常像结果一样深刻，严厉的活动——特别是为了证实具备程序员资格的活动——变得过时了。结果，缺乏经验的测试员所做的事情就像一个局部可编程编辑器专家或是一个复杂的自由软件工具专家所做的事情一样。这些虽然与测试无关，但至少还有潜在的作用。更危险的是误导了测试活动，即测试自动化。(参见最后一个主题)

　　Even if novice testers were well guided, having so much of the testing staff be transients could only work if testing is a shallow algorithmic discipline. In fact, good testers require deep knowledge and experience.

　　即使新测试员很好地获得指导，除非测试是一个浅显的算法学科，否则将这么多测试人员转换工作也是不可行的。事实上，好的测试员需要深入的知识与经验。

　　The second classic mistake is recruiting testers from the ranks of failed programmers. There are plenty of good testers who are not good programmers, but a bad programmer likely has some work habits that will make him a bad tester, too. For example, someone who makes lots of bugs because he's inattentive to detail will miss lots of bugs for the same reason.

　　第二个典型错误是从不合格的程序员中招募测试员。有很多好的测试员都不是好的程序员，但一个不好的程序员的一些工作习惯可能使他也会成为一个不好的测试员。例如，一个因为不注重细节的而产生很多 bug 的人也会因为同样的原因而漏掉很多 bug 。

　　So how should the testing team be staffed? If you're willing to be part of the training department, go ahead and accept new programmer hires. Accept as applicants programmers who you suspect are rejects (some fraction of them really have gotten tired of programming and want a change) but interview them as you would an outside hire. When interviewing, concentrate less on formal qualifications than on intelligence and the character of the candidate's thought. A good tester has these qualities:

　　那么应该如何招募测试团队呢?如果你愿意成为一个培训部门，可以继续接受一些新程序员。接受一些你怀疑是被其他人舍弃的程序员申请人(他们之中确实有一些人是厌倦了编程而想有一些变化)，但是像从公司外面招人一样面试他们。在面试的时候，重点集中于应聘者的智力和思想特征而不是表面的资历。一个好测试员应该具备：

　　· methodical and systematic.

　　· 有条理、有计划。

　　· tactful and diplomatic (but firm when necessary).

　　· 有策略、说话办事得体(但在需要的时候要坚定)

　　· skeptical, especially about assumptions, and wants to see concrete evidence.

　　· 怀疑能力，特别是关于假设的，并要看到具体证明。

　　· able to notice and pursue odd details.

　　· 能够注意并跟踪奇怪的细节之处。

　　· good written and verbal skills (for explaining bugs clearly and concisely).

　　· 良好的书面和口头表达技巧(可以清楚、简洁地解释 bug )。

　　· a knack for anticipating what others are likely to misunderstand. (This is useful both in finding bugs and writing bug reports.)

　　· 能够预料到其他人可能会误解什么的能力(这在发现 bug 和编写 bug 报告时非常有用)

　　· a willingness to get one's hands dirty, to experiment, to try something to see what happens.

　　· 愿意不辞辛苦地进行实验，尝试一些事情来看看会发生什么。

　　Be especially careful to avoid the trap of testers who are not domain experts. Too often, the tester of an accounting package knows little about accounting. Consequently, she finds bugs that are unimportant to accountants and misses ones that are. Further, she writes bug reports that make serious bugs seem irrelevant. A programmer may not see past the unrepresentative test to the underlying important problem. (See the discussion of reporting bugs in the next theme.)

　　特别是要小心避免测试员不是领域专家的陷阱。经常地，会计软件包的测试员对会计了解很少。结果是，她发现的 bug 对于会计师来说不重要，但又漏掉了很多对于会计师来说很重要的 bug 。而且，她编写的 bug 报告将使严重的 bug 看起来无关紧要。程序员可能无法透过不具备代表性的测试来看到底层的重要问题(查看下一主题中的关于报告 bug 的讨论。)

原文转自：http://www.uml.org.cn/Test/200709289.asp