Don’t assume that everyone will use the function library just because it’s there. Some people code in different styles from each other. If you don’t have programming standards that cover variable naming, order of parameters in function interfaces, use of global variables, etc., then what seems reasonable to one person will seem unacceptable to another. Also, some people hate to use code they didn’t write. Others come onto a project late and don’t know what’s in the library. Working in a big rush, they start programming without spending any time with the library. You have to manage the use of the library.
不要認為每個人使用函數庫僅僅是因為它已經存在。有的人的編碼風格與其他人就不同。如果你沒有一個編程標準來控制變量命名、函數接口的參數順序、全局變量的使用等等，那么在一個人看來合理的東西在另一個看來將變的不可接受。此外，有的人不喜歡使用不是他們編寫的代碼。而另一些人由于參與項目較晚而不知道庫中的內容，于是就倉促的在沒有了解庫的情況下開始編程。因此，你必須管理好庫的使用。
Finally, be careful about setting expectations, especially if your programmers write their own custom controls. In Release 1.0 (or in the first release that you start automating tests), you will probably spend most of your available time creating a framework that encapsulates all the crazy workarounds that you have to write just to press buttons, select list items, select tabs, and so on. The payoff from this work will show up in scripts that you finally have time to write in Release 2.0. Framework creation is expensive. Set realistic expectations or update your resume.
最后，要慎重設置期望值，尤其在當你的程序員編寫了他們自己定制的控件時。在發行版1.0(或你開始自動化測試的第一個發行版)中，你很可能會花費很多時間來創建一個封裝了所有工作區的框架，以至你不得不編寫點擊按鈕、選擇表項、選擇tab鍵的代碼。這些工作的回報將在你最后花時間編寫的發行版2.0中體現出來。創建框架的開銷很大，因此，要設置符合實際的期望值或修正你的摘要。
5. Recognize staffing realities.
5.按真實情況安排崗位
You must educate your management into several staffing issues.
你必須讓管理者注意下面幾個問題。
First, many testers are relatively junior programmers. They don’t have experience designing systems. Poorly designed frameworks can kill the project too. So can overly ambitious ones. To automate successfully, you may have to add more senior programmers to the testing group.
首先，很多測試人員都是相對初級的程序員。他們缺乏設計系統的經驗，而設計不良的框架則會扼殺項目。但是，太有能力的程序員也會使項目失敗。要使自動化成功，你應該在你的測試組中多招募一些高級程序員。
Second, many excellent black box testers have no programming experience. They provide subject matter expertise or other experience with customer or communications issues that most programmers can’t provide. They are indispensable to a strong testing effort. But you can’t expect these people to write automation code. Therefore, you need a staffing and development strategy that doesn’t require everyone to write test code. You also want to avoid creating a pecking order that places tester-programmers above tester-non-programmers. This is a common, and in my view irrational and anti-productive, bias in test groups that use automation tools. It will drive out your senior non-programming testers, and it will cost you much of your ability to test the program against actual customer requirements.
文章來源于領測軟件測試網 http://www.kjueaiud.com/
