Understanding Test Engineers (TE) and the ACC Testing Method in Google’s Software Testing Approach
The article analyzes Google’s definition of Test Engineers, compares it with domestic testing roles, discusses why test plans fade, and introduces the ACC (Attribute‑Component‑Capability) method as a practical alternative for quality assurance in modern software development.
This piece interprets Chapter 3 of *How Google Tests Software*, focusing on the role of Test Engineers (TE) and how Google positions them as engineers who evaluate user impact and software‑wide risk.
TE goals are user‑centric, contrasting with SET’s product‑oriented tooling focus; TE must possess strong technical skills to influence developers, highlighting a universal issue that technical competence often determines status.
The author presents a pressure/requirement chain: product managers drive revenue, which forces quality from the user perspective, leading to product‑level quality capabilities, which then require tools and solutions.
A comparison with Chinese testing structures shows two domestic patterns: one where business testing shoulders product quality and passes pressure to developers, and another where quality pressure goes directly to developers while business testing acts as a side lane, often resulting in ineffective tools.
The article argues that test plans are not disappearing but are fragmented into daily work due to rapid release cycles and micro‑service complexity.
It introduces the ACC method (Attribute, Component, Capability) as a replacement for traditional test plans: Attribute describes product qualities, Component identifies system modules, and Capability defines measurable actions, each guiding test design.
Examples illustrate how to apply ACC to a video app like Douyin, mapping traits (smooth playback) to components (player module, CDN) and capabilities (startup time, buffering rate).
The discussion emphasizes that components must be testable, sometimes requiring “back doors” from developers to achieve observability.
Finally, the ACC workflow is summarized: identify product attributes, decompose into components, define capabilities, then derive test methods, showing clear logical chains, concise scope, and comprehensive expectations for Test Engineers.
The series concludes that while many ideas are inspiring, they must be adapted to local contexts rather than copied verbatim.
Byte Quality Assurance Team
World-leading audio and video quality assurance team, safeguarding the AV experience of hundreds of millions of users.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.