What We Learned Building Youzan’s Testing Team – Insights Behind Our New Ebook

Background

In early 2014, Youzan, a rapidly growing tech company that had written its first line of code in November 2012, began forming a dedicated testing team despite already having a sizable engineering staff of over fifty people focused only on front‑end and back‑end development.

Why a Dedicated Testing Team?

Industry norms would suggest a ratio of one tester for every five to eight engineers, yet Youzan initially operated without any testers. The company’s philosophy emphasized that bugs are created by developers, not discovered by testers, reinforcing the principle that the coder bears primary responsibility for quality.

Hiring Code‑Savvy Testers

When assembling the team, Youzan deliberately recruited testers who could also write code—what is now called test development engineers. At the time, such talent was scarce and expensive, especially for a startup with limited revenue, but the leadership believed that investing in technically proficient testers would yield greater long‑term efficiency and scalability.

Strategic Rationale

The decision to prioritize code‑capable testers over pure functional testers was driven by a forward‑looking view: functional testing roles were expected to have limited growth over the next five to ten years. By hiring engineers who could automate tests, contribute to CI/CD pipelines, and handle performance analysis, the team could achieve ten‑fold productivity gains compared to average engineers.

Team Growth and Impact

Within roughly a year, the testing team established a complete talent ladder and earned recognition within the Hangzhou tech community. Their deep involvement across projects gave them extensive business and scenario knowledge, producing many senior technical leaders who later assumed broader responsibilities.

Because the team consisted of developers‑testers, responsibilities that previously required multiple roles—such as basic security (offense/defense), early development efficiency initiatives (CI, CD), and stability assurance (full‑stack load testing, performance analysis)—converged into a single role. This consolidation saved significant time, effort, and cost before the organization formalized specialized positions.

Long‑Term Value Perspective

The article argues that short‑term problem solving often yields limited returns, whereas investments made with a five‑year or longer horizon begin to generate measurable “profits” after a few years. The testing team’s achievements exemplify this principle, as their sustained effort has produced high‑quality outputs and industry influence.

Conclusion

The author emphasizes that while the team’s practices are shared as a reference, they may not suit every organization; readers should adapt the ideas to their own contexts. The piece ends with gratitude to the community and an invitation for feedback, underscoring the collaborative spirit behind the team’s success.