How to View Research‑Test Integration and the Future Development of Software Testing

Welcome to the "UC International Technology" public account, which provides high‑quality technical articles on client‑side, server‑side, algorithms, testing, data, front‑end, and more, including original and translated content.

The author, De Bao, a senior test development expert at Alibaba and head of the UC International R&D testing team, shares his perspective on research‑test integration and the development of software testing.

Two key topics are discussed: how to view research‑test integration and how to view the development of software testing.

Research‑test integration emerged to address communication gaps and conflicts between independent testing and development teams that caused frequent version delays. By embedding testers within development teams, communication improved and iteration speed increased, but many testers feel their growth and ownership of quality are neglected.

Missing focus areas include the lack of attention to tester development, unclear test team positioning, and insufficient adaptation to changing business scales, leading to quality degradation.

Regarding the future of software testing, the article outlines the "three‑year itch" many testers experience, the expanding scope of testing from version verification to service quality assurance, and the importance of understanding the concept of "good enough" versus true quality.

It highlights concerns about the diminishing role of dedicated test engineers in large tech companies, while emphasizing that as systems become more complex and critical, the need for skilled testers will grow.

The piece introduces the SDET (Software Development Engineer in Test) role as a hybrid of testing and development, capable of building testing platforms and tools.

It also discusses the challenges of "de‑TE" (removing test engineers) in China due to limited quality infrastructure, intense competition, and insufficient testing maturity.

Finally, the article offers practical advice for test engineers: understand company testing positioning, take on more responsibilities, embrace building tools (even if it feels like reinventing the wheel), and develop management skills focused on tasks rather than people.

Overall, the article encourages test engineers to stay ahead of industry changes, continuously improve their skills, and avoid being left behind.