测试自动化的19个教训

Elfriede Dustin在总结了多年的自动化测试项目经验后，提出了19个经验教训：

　　(1)在软件开发周期中使用的各种工具不能够很轻易地整合在一起。(The various tools used throughout the development lifecycle did not easily integrate)

　　(2)很多冗余的信息被存储在多个库中。(Duplicate information was kept in multiple repositories)

　　(3)被测试工具圈着鼻子走。(The automated testing tool drove the testing effort)

　　(4)整个测试组的每个人都在忙着编写自动化测试脚本。(Everyone on the testing staff was busy trying to automate scripts)

　　(5)重复开发的劳动，尝试编写一些非常复杂的测试脚本。(Elaborate test scripts were developed, duplicating the development effort)

　　(6)自动化测试脚本的创建往往会很麻烦，而不像工具厂商所吹嘘的那样简单易用。(Automated test script creation was cumbersome)

　　(7)工具的培训开展得太迟，测试工程师缺乏工具方面的知识。(Training was too late in the process , so test engineers lacked tool knowledge)

　　(8)测试工具在系统测试前两周才引入。(The test tool was introduced to the testing program with two weeks left for system testing)

　　(9)测试人员对工具有抵触情绪。(Testers resisted the tool)

　　(10)对自动化测试的期待值过高，期待及早得到回报。(There were expectations of early payback)

　　(11)工具在识别第三方控件方面存在问题。(The tool had problems recognizing third-party controls (widgets))

　　(12)缺乏测试脚本开发的规范性指南。(A lack of test development guidelines was noted)

　　(13)某些测试工具需要插入代码到被测试程序中，但是开发人员直到测试后期才被告知这个问题。(The tool was intrusive, but the development staff wasn’t informed of this problem until late in the testing lifecycle)

　　(14)工具创建的报告没什么用处。(Reports produced by the tool were useless)

　　(15)在尚未确定系统工程环境之前就选择和购买工具。(Tools were selected and purchased before a system engineering environment was defined)

　　(16)工具的不同版本都在使用。(Various tool versions were in use)

　　(17)工具的升级与现有的系统工程环境不兼容。(The new tool upgrade wasn’t compatible with the existing system engineering environment)

　　(18)工具的数据库不允许扩展。(The tool’s database didn’t allow for scalability)

　　(19)未能正确地使用测试工具的管理功能，导致时间的浪费。(Incorrect use of a test tool’s management functionality results in wasted time)

• 通信类测试无线通讯名词解释[2]
• 通信类测试无线通讯名词解释[1]
• 项目管理中的需求变更控制分析[3]
• 项目管理中的需求变更控制分析[2]
• 项目管理中的需求变更控制分析[1]