Master
ThoughtWorks
菜单
关闭
  • 产品及服务
    • 概况
    • 客户体验与产品设计业务线
    • 数据战略、工程及分析业务线
    • 数字化转型及运营业务线
    • 现代化企业、平台及云业务线
  • 合作伙伴
    • 概况
    • 汽车企业
    • 医疗企业
    • 公共服务机构
    • 清洁技术,能源与公用事业
    • 媒体和出版业
    • 零售业和电商
    • 金融和保险企业
    • 非盈利性组织
    • 旅游业和运输业
  • 洞见
    • 概况
    • 特色

      • 技术

        深入探索企业技术与卓越工程管理

      • 商业

        及时了解数字领导者的最新业务和行业见解

      • 文化

        分享职业发展心得,以及我们对社会公正和包容性的见解

    • 数字出版物和工具

      • 技术雷达

        对前沿技术提供意见和指引

      • 视野

        服务数字读者的出版物

      • 数字化流畅度模型

        可以将应对不确定性所需的数字能力进行优先级划分的模型

      • 解码器

        业务主管的A-Z技术指南

    • 所有洞见

      • 文章

        助力商业的专业洞见

      • 博客

        ThoughtWorks 全球员工的洞见及观点

      • 书籍

        浏览更多我们的书籍

      • 播客

        分析商业和技术最新趋势的精彩对话

  • 加入我们
    • 概况
    • 申请流程

      面试准备

    • 毕业生和变换职业者

      正确开启技术生涯

    • 搜索工作

      在您所在的区域寻找正在招聘的岗位

    • 保持联系

      订阅我们的月度新闻简报

  • 关于我们
    • 概况
    • 我们的宗旨
    • 奖项与荣誉
    • 多元与包容
    • 领导层
    • 合作伙伴
    • 辅助功能
    • 新闻
  • 联系我们
China | 中文
  • United States United States
    English
  • China China
    中文 | English
  • India India
    English
  • Canada Canada
    English
  • Singapore Singapore
    English
  • United Kingdom United Kingdom
    English
  • Australia Australia
    English
  • Germany Germany
    English | Deutsch
  • Brazil Brazil
    English | Português
  • Spain Spain
    English | Español
  • Global Global
    English
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
软件测试London技术

The QA Role - What Is It Really?

Kenny Cruden Kenny Cruden

Published: May 19, 2015

On several occasions I’ve witnessed companies, who have decided to develop software using agile methodologies, view the QA role in teams as basically a waterfall tester who is involved with automated tests.

By this I mean someone who performs all the manual testing of the product required within the team, and who is also exposed to test code (the latter depends on many factors, and is explained fully here).

In my opinion, this description does a disservice to the breadth and depth of what I view the QA role to be. I often spend a fair amount of my time with clients explaining all the other facets of the role as well, and the value that each brings to the team and the product.

Having done this several times, I found it beneficial to create a one-page picture as a visual prompt to assist me in this discussion. It’s shown below and descriptions of each section follow it :-

The Title

The statement at the top and bottom is a summation of what a QA brings to the project, the mindset of "Are we building the correct product and, if so, are we building it correctly?". A person in this role is someone who consistently questions all parts of the process to ensure the team is producing the desired output.

My personal preference is to not use the word “Quality” here, and instead use “Correct”. By using “correct”, I am provided with a much better idea of what to focus on.

An example is if the user interface of a call centre application looks terrible from an aesthetic perspective - the colour scheme makes it hard to discern boundaries, poor sequential flow, large numbers of clicks and scrolling required etc. It is, however, perfect for people to tab through and in this case, as that is the only way that users will interact with it, then it is the correct product for the customer.
Using the word “quality” means many things to many people - using “correct” minimises the possible ambiguity of having multiple opinions in a team.

Principles

The image on the top left is to help in discussing the strategy and construction of maintainable test frameworks. The embodiment of this principle is the test pyramid.

The image on the top right represents what a QA is constantly thinking about and discussing with the team, story by story. It does not reflect that they are actively involved in all the activities.

Practices

The image in the middle represents the lifecycle of a story from a QA perspective, and each of the touchpoints they will be involved in.

Comparing these touchpoints during the lifecycle of a story with those of a ‘waterfall tester involved with automated tests’ highlights the additional scope of the role. Rather than it being a critique of what has already been built, the role encompasses looking to what’s coming up and ensuring the idea and description is sufficient.

Environments

The image on the bottom left is to help explain, from an environment perspective, the activities that reduce risk and help the team gain confidence that they’re building the correct product. Each environment provides the platform for unique validations to be made, each providing a different benefit and focus on the product.

Breadth and Depth of the Role

The image on the bottom right is to help explain that no QA is exactly the same. Some people in the role have a deep understanding of the Iteration Manager role and can seamlessly step into that role if required. Some can work as a BA without any need for further training, some can take on the UX role and some the developer role. Everyone has a unique mix of all these capabilities.

What is important to note is that a QA has a fundamental understanding of each of the roles in the team and, as such, is a ‘generalist by trade’. They require this broad understanding of the roles to be able to understand how projects and their products are progressing and, as a result, provide feedback on practices or processes that could be improved. And, above all, inform the team about whether the product under development is what the customer wants.

I hope this diagram encapsulates the essence of what you believe the QA role is as well, and assists in any discussions you may have on the topic.

Master
政策声明 | 现代奴役声明 | 辅助功能
Connect with us
×

WeChat

QR code to ThoughtWorks China WeChat subscription account
© 2021 ThoughtWorks, Inc.