典型的測試錯誤有哪些？(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