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.
文章来源于领测软件测试网 https://www.ltesting.net/
