典型的測試錯誤有哪些？(10)

　　Domain experts may be hard to find. Try to find a few. And hire testers who are quick studies and are good at understanding other people's work patterns.

　　領域專家可能不太好找。嘗試去找幾個。聘用那些能夠快速學習并且善于理解他人工作方式的測試員。

　　Two groups of people are readily at hand and often have those skills. But testing teams often do not seek out applicants from the customer service staff or the technical writing staff. The people who field email or phone problem reports develop, if they're good, a sense of what matters to the customer (at least to the vocal customer) and the best are very quick on their mental feet.

　　有兩組人員比較容易找并且常常具備這些技能。但是測試小組經常不從客戶服務人員或技術文檔寫作人員中尋求申請人。通過郵件或電話解決問題報告的人，如果是稱職的，那么他們知道對于客戶(至少是電話中的客戶)來說什么是重要、最好的，這種感覺對他們將有所幫助。

　　Like testers, technical writers often also lack detailed domain knowledge. However, they're in the business of translating a product's behavior into terms that make sense to a user. Good technical writers develop a sense of what's important, what's confusing, and so on. Those areas that are hard to explain are often fruitful sources of bugs. (What confuses the user often also confuses the programmer.)

　　像測試員一樣，技術寫作人員常常也缺乏詳細的領域知識。但是，他們的工作是將產品的特性以對用戶有意義的方式轉換出來。一個好的技術寫作人員有培養出一種什么是重要的、什么是令人迷惑的感覺。那些難于解釋的領域經常包含了很多的測試錯誤。(使用戶感到迷惑的地方同樣也會使程序員感到迷惑。)

　　One reason these two groups are not tapped is an insistence that testers be able to program. Programming skill brings with it certain advantages in bug hunting. A programmer is more likely to find the number 2,147,483,648 interesting than an accountant will. (It overflows a signed integer on most machines.) But such tricks of the trade are easily learned by competent non-programmers, so not having them is a weak reason for turning someone down.

　　沒有選擇這兩組人員的一個原因是堅持認為測試員都應當會編程。編程技巧會給搜尋 bug 帶來一定的優勢。與財務人員相比，程序員更有可能發現數字2,147,483,648是有趣的(這個數字在大多數機器的有符號整數中溢出。)但是這種技巧很容易被有能力的非程序員掌握，所以這是不錄取他們的一個不充分的理由。

　　If you hire according to these guidelines, you will avoid a testing team that lacks diversity. All of the members will lack some skills, but the team as a whole will have them all. Over time, in a team with mutual respect, the non-programmers will pick up essential tidbits of programming knowledge, the programmers will pick up domain knowledge, and the people with a writing background will teach the others how to deconstruct documents.

　　如果你按照這些規則招聘員工，你就會避免一個缺乏多樣性的測試小組。所有的成員都會缺乏某些技能，但作為一個整體，小組應當具備這些所有的技能。隨著時間的推移，在一個互相尊重的的小組中，非程序員將獲取一些最基礎的編程知識，程序員將獲得專業領域知識，而具有寫作背景的人將教會其他人如何解構、拆析文檔。

　　All testers - but non-programmers especially - will be hampered by a physical separation between developers and testers. A smooth working relationship between developers and testers is essential to efficient testing. Too much valuable information is unwritten; the tester finds it by talking to developers. Developers and testers must often work together in debugging; that's much harder to do remotely. Developers often dismiss bug reports too readily, but it's harder to do that to a tester you eat lunch with.

　　所有的測試員——尤其是非程序員——會被開發人員和測試員在物理位置上的隔離所困擾。開發人員和測試員之間和諧的工作關系對于有效測試來說至關重要。太多有價值的信息沒有記錄下來;測試員在與開發人員交談時發現了它。開發人員與測試員必須在一起工作以排除 bug ，遠程實現是非常困難的。開發人員常常隨意關閉一個 bug 報告，但是對一個一起吃午餐的測試員的報告卻很難這樣做。

　　Remote testing can be made to work - I've done it - but you have to be careful. Budget money for frequent working visits, and pay attention to interpersonal issues.

　　遠程測試也能達到目的——我就這樣做過——但你必須很小心。經常進行工作訪問的資金預算，并且要注意人際關系問題。

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