51Testing软件测试论坛

 找回密码
 (注-册)加入51Testing

QQ登录

只需一步,快速开始

微信登录,快人一步

查看: 10124|回复: 0

【推荐原文】How to choose a functional testing tool: 7 key considerations

[复制链接]
  • TA的每日心情
    慵懒
    2019-2-2 13:49
  • 签到天数: 242 天

    连续签到: 1 天

    [LV.8]测试军长

    发表于 2017-10-30 16:43:58 | 显示全部楼层 |阅读模式
    原文作者:Matthew Heusser
    作者联系方式:
    原文地址链接:https://techbeacon.com
    推荐理由:对测试工具的选择很有帮助


      Type "test tool, how do I pick one?" into Google, and you'll find a wide variety of answers, from open source to best of breed—based on many different assumptions. One result assumes an ideal situation where you need a GUI-based test tool that does not require programming, while another claims that automated tests are code, and a third is more interested in test tooling as examples and documentation that just happens to be executable.
      According to Connor Roberts, director of quality and testing for Liquidity Services, organizations sometimes introduce or swap testing tools just because a new manager had experience with a tool at a previous company, or just to save money and look better on the budget sheet.
      "Teams that end up using it every day finds themselves with the same frustrations as before, just in a slightly different flavor."
      —Connor Roberts
      The failure: Not asking if the tool actually addresses the problems the team needs to solve.
      Tool selection is often based on criteria that are less than optimal. So what are the right ones? Here are seven key things you to consider when choosing a functional testing tool.
      1. Defect categories
      What are the showstopper bugs that appear, and where do they appear? That's an easy enough question to ask; most teams with a bug tracker can find the answer over a lunch hour. That kind of research might find the majority of bugs in the business logic, the database layer, or the graphical user interface (GUI).
      If the more important bugs are in the GUI, then test automation of the business logic through unit tests won't add much value. It certainly won't be the first place to start.
      Although this is the first question, it can also be the last. After selecting a tool, return to this question. Review the recent defects that matter, found both in test and in production, and ask if the tool realistically could catch those types of defects. If the answer is "probably not" or worse, then restart the tool selection process.

    ......

    (下载附件即可查看原文)
    【申请翻译方式】
    ① 发送一段试译内容到我们的邮箱 editor@51testing.com,通过后即可翻译
    ② 加小编 QQ:1718403480,备注:翻译试译


    【翻译奖励】
    ① 翻译文章经过评审入选后,即可发布在《51测试天地》电子刊物中,并有相应稿费支付!还有机会上网站头条,得到大力宣传!
    ② 未入选文章,联系小编(QQ:1718403480),也可以获得博为峰网校10元代金券

    如果你想锻炼自己的翻译能力,或者想学习最新最热的技术内容,欢迎加入到我们的翻译队伍中来!!

    本帖子中包含更多资源

    您需要 登录 才可以下载或查看,没有帐号?(注-册)加入51Testing

    x
    回复

    使用道具 举报

    本版积分规则

    关闭

    站长推荐上一条 /1 下一条

    小黑屋|手机版|Archiver|51Testing软件测试网 ( 沪ICP备05003035号 关于我们

    GMT+8, 2024-3-19 19:51 , Processed in 0.068862 second(s), 26 queries .

    Powered by Discuz! X3.2

    © 2001-2024 Comsenz Inc.

    快速回复 返回顶部 返回列表