• 软件测试技术
  • 软件测试博客
  • 软件测试视频
  • 开源软件测试技术
  • 软件测试论坛
  • 软件测试沙龙
  • 软件测试资料下载
  • 软件测试杂志
  • 软件测试人才招聘
    暂时没有公告

字号: | 推荐给好友 上一篇 | 下一篇

改进自动化测试套件的可维护性(四)

发布: 2010-6-13 10:56 | 作者: 不详 | 来源: 领测国际采编 | 查看: 16次 | 进入软件测试论坛讨论

领测软件测试网

  You might find it productive to work primarily at one level, adding test cases for other levels only when you clearly need them.

  你会发现主要在一个级别上工作是高效的。所以,只有当你明确了需要在其它级别上添加测试用例后,才可以这么做。

  There are plenty of other ways to define and split levels. Analyze the task in whatever way is appropriate. The issue here is that you want to avoid randomly shifting from creating very simple tests to remarkably long, complex ones. (Consensus)

  还有很多定义和区分级别的其他方法。而无论用什么方法,分析任务总是合适的。这里要注意的是,需要避免随意地从创建十分简单的测试变成创建特别冗长复杂的测试。(一致同意)

  24. Scripts loaded into the framework’s function library should generally contain error checking. (Consensus) 被载入框架的函数库的脚本一般应该包括错误检查功能。(一致同意)

  This is good practice for any type of programming, but it is particularly important for test code because we expect the program that we’re testing to be broken, and we want to see the first symptoms of a failure in order to make reporting and troubleshooting easier.

  这是任何类型编程都能得到的好经验,但是对于测试代码尤其显得重要。因为,我们希望我们测试的程序出现问题,并且,为了使报告和排除故障变得容易,我们希望看到失败的最初征兆。

  25. When creating shared library commands, there are risks in dealing with people’s differing programming and documentation styles. People will not use someone else’s code if they are not comfortable with it.(Consensus)

  当创建共享库命令时,就会出现处理不同编码和文档风格的问题。因为如果人们对某人的代码不满意,他们就不会使用它。(一致同意)

  26. Beware of "saving time" when you create a scripts by circumventing your library. Similarly, beware of not creating a library. (Consensus)

  在通过包绕函数库创建脚本时,要注意节省时间。与此类似,要注意不要创建单独的一个库。(一致同意)

  The library is an organized repository for shared functions. If a function is too general, and requires the user to pass it a huge number of parameters, some programmers (testers who are doing automation) will prefer to use their own special-purpose shorter version. Some programmers in a hurry simply won’t bother checking what’s in the library. Some programmers won’t trust the code in the library because they think (perhaps correctly) that most of it is untested and buggy.

  函数库是一个有组织的共享函数储藏区。如果有个函数太全面,需要用户向它传递大量的参数,那么一些程序员(正在做自动化的测试者)就可能会使用他们自己特定目的的较小版本。而有的程序员由于匆忙,不在意检查库中的代码。还有的程序员则不信任库中的代码,因为他们觉得(或许是正确的)库里的大部分东西没有被测试过,存在着bug。

  27. It is desirable to include test parameters in data files such as .ini files, settings files, and configuration files rather than as constants embedded into the automation script or into the file that contains the script. (Consensus)

文章来源于领测软件测试网 https://www.ltesting.net/


关于领测软件测试网 | 领测软件测试网合作伙伴 | 广告服务 | 投稿指南 | 联系我们 | 网站地图 | 友情链接
版权所有(C) 2003-2010 TestAge(领测软件测试网)|领测国际科技(北京)有限公司|软件测试工程师培训网 All Rights Reserved
北京市海淀区中关村南大街9号北京理工科技大厦1402室 京ICP备2023014753号-2
技术支持和业务联系:info@testage.com.cn 电话:010-51297073

软件测试 | 领测国际ISTQBISTQB官网TMMiTMMi认证国际软件测试工程师认证领测软件测试网