The article explains why testing aims to ensure software quality, outlines how testers can avoid being blamed by documenting bugs, following clear hand‑off processes, collaborating on urgent test items, and fostering a team culture of responsibility and continuous improvement.
This article presents a scenario‑driven methodology for scaling intelligent testing through the five core testing phases—input, execution, analysis, localization, and evaluation—detailing how AI techniques enhance coverage, efficiency, fault detection, and risk assessment.
This article explains why automation testing is essential for modern software projects, compares it with manual testing, outlines common test types, offers strategic guidance on frameworks and tool selection, and explores emerging trends such as AI and RPA shaping the future of testing.
This talk shares Yuque’s experience building an Electron‑based desktop product, covering why Electron was chosen, the app’s architecture, and engineering practices—including unit testing, integration‑test coverage, package and data security, update strategies, and full‑link logging—to improve code quality and runtime stability.
This article details how a C++‑based cross‑platform framework was designed for WeChat Pay to unify iOS and Android implementations, improve scalability, quality assurance, and developer productivity through use‑case abstraction, a routing mechanism, and refined network and data handling.
vivo’s “Moonlight Treasure Box” platform records and replays production traffic using a customized Jvm‑Sandbox‑Repeater Java‑Agent, handling GC limits, thread‑pool tracing, data desensitization, deduplication, timestamp alignment, noise reduction and sub‑call matching, while providing plugins, visual call‑chain analysis and coverage metrics that have integrated 200 services, executed over 10 000 sessions, and boosted testing efficiency by more than 80 %.
Youzan boosted mobile product reliability by instituting proactive anomaly detection, rigorous unit‑testing and CI, a disciplined betterMR review workflow, and dedicated performance monitoring to meet offline and hardware constraints, cutting incident volume to one‑third and fostering a virtuous cycle of stability and team morale.
This article examines the challenges of traditional API automation testing and presents an intelligent testing approach that combines data and algorithms to optimize the entire API test lifecycle, improving efficiency, maintainability, and quality through automated case generation, execution, analysis, and evaluation.
This article shares a former Alibaba test‑development graduate’s path—from choosing the QA role, preparing for the interview, and navigating the first year’s challenges to leading large‑scale projects—offering practical insights and advice for aspiring QA professionals.
This article explores three critical questions for software testing—effectiveness, efficiency, and value—by examining how to assess test validity, improve execution speed through environment and infrastructure optimization, and demonstrate testing’s role in building quality, exposing risk, and enforcing quality gates.
The article outlines the background, mission, technical choices, and comprehensive features of the Tianyan Quality Platform—an internal testing solution built with Vue and Spring Boot that streamlines API automation, environment management, and DevOps integration across multiple business lines.
This comprehensive guide outlines the purpose, scope, principles, quality standards, management processes, design methods, review procedures, and risk analysis for creating effective software test cases, helping teams ensure coverage, reliability, and maintainability throughout the testing lifecycle.
This document provides a complete, structured template for a software test report, covering purpose, system overview, test environment, test summary, defect analysis, security testing, and improvement suggestions, with placeholders for data, tables, and visual charts to guide thorough quality assessment.
This comprehensive guide outlines the end‑to‑end software testing lifecycle—including purpose, scope, detailed test phases, deliverables, reporting, acceptance criteria, and closure activities—to help teams plan, execute, and manage high‑quality testing processes effectively.
This guide walks through every phase of testing in a software development lifecycle—from planning and requirement analysis, through test design, execution, integration, and acceptance, to coverage evaluation, defect analysis, and final reporting—providing practical methods, metrics, and best‑practice templates for quality assurance professionals.
This article outlines a comprehensive competency framework for test engineers, detailing five proficiency levels—basic understanding, proficient, flexible application, comprehensive application, and innovative mastery—across 28 key testing activities such as analysis, design, planning, execution, automation, security, and DevOps, providing clear behavioral descriptions for each level.
This article explains the distinct concepts of code coverage and test coverage, outlines their respective measurement methods, compares their advantages and disadvantages, and provides guidance on selecting appropriate tools and practices for effective software quality assurance.
This article explains how the Apollo testing framework was redesigned to enable scenario‑based API testing, reduce case creation and maintenance costs, improve quality checks, and support advanced features like traffic replay, ultimately enhancing automation efficiency for large‑scale business services.
This article outlines a comprehensive testing strategy for mobile app push notifications, describing the push workflow, key test points such as message receipt and app launch, and detailing the implementation of push sending and reachability analysis tools, along with future enhancements for monitoring and diagnostics.
iQIYI integrated JaCoCo with its DevOps pipeline, using Git diff and Jira‑linked branch naming to automatically generate fine‑grained coverage reports at incremental, branch, and requirement levels, enforcing 90 % thresholds that lifted backend service coverage from under 70 % to over 90 % and markedly improved reliability.
This article explains why traditional end‑stage design reviews are insufficient, introduces the concept of Design QA throughout the product lifecycle, and outlines a step‑by‑step implementation plan—including requirement grading, extreme‑case handling, integrated specs, test‑case reviews, and walkthrough documentation—to ensure consistent design quality.
This article examines the shortcomings of traditional regression testing, introduces a precise testing framework that combines black‑box and white‑box techniques, outlines its core principles, evolution steps, and measurement methods, and shares practical outcomes and future directions for server‑side quality assurance.
This article explains how systematic unit testing boosts R&D efficiency, outlines its origins, methods, tools, and evaluation standards, and shares practical insights from JD Retail specialists on implementing effective unit tests in real‑world projects.
This article explains why test cases are essential, outlines the complete workflow from requirement analysis to case maintenance, and provides practical tips and tool recommendations—including Excel and Xmind—to help testers design, review, and manage high‑quality test cases efficiently.
The article analyzes common reasons why defects escape testing and appear in production—ranging from missed test cases and environment differences to incomplete releases—and offers a step‑by‑step checklist of practices to improve testing, release processes, and risk mitigation.
YouZan’s traffic‑replay platform records real production calls and replays them in test environments—both read‑only and mock‑write modes—to automatically verify thousands of marketing interfaces, visualize scenario coverage, capture low‑traffic cases, and has already enabled zero post‑launch failures while guiding future expansion into deeper coverage and performance testing.
The MTSC2021 Shenzhen conference, a premier software testing summit organized by TesterHome, will be held on November 19‑20, 2021 at the Dongxi Road International Hotel in Shenzhen, offering registration information, audience guidance, participant benefits, and a comprehensive list of confirmed and candidate technical topics covering testing, DevOps, AI, cloud, and game development.
China Bank’s software center shares how its enterprise‑grade DevOps cloud platform passed the national DevOps standard assessment with excellent ratings, boosting build success rates, reducing deployment times, and driving a culture of secure, end‑to‑end continuous delivery across the bank.
The article shares a tester’s two‑year growth experience, illustrating how testing focus shifts from basic functional checks to comprehensive test plans that combine interface, data‑construction, mock, and debugging techniques for various backend, frontend, and full‑stack scenarios.
The Creation Quality Platform (CQ) automates large‑scale detection of templates, mini‑programs, and special‑effect resources across ByteDance apps, combining automated pipelines, algorithmic classification, CV/NLP checks, and prioritized task routing to boost efficiency, accuracy, and creator experience while reducing manual effort.
The article outlines Google’s best‑practice guidelines for code coverage, emphasizing its workflow benefits, the cultural impact of increasing coverage, the limits of high percentages, the importance of uncovering uncovered code, and practical steps for progressively improving coverage across projects.
Users uninstall apps when friction—such as privacy worries, useless features, crashes, slow performance, or intrusive ads—overrides desire, so applying a five‑level APP experience pyramid (Security, Functionality, Stability, Usability, Delight) with privacy checklists, exploratory testing, full‑stack monitoring, and real‑user usability sessions can markedly boost retention.
This article explains agile testing, contrasts it with traditional testing, and details ten guiding principles—including continuous feedback, customer value, face‑to‑face communication, courage, simplicity, continuous improvement, adaptability, self‑organization, people focus, and enjoyment—that help testers and agile teams deliver high‑quality software efficiently.
This article outlines a thorough methodology for evaluating software, hardware, and overall system architectures, detailing assessment criteria, a five‑stage evaluation process, quality‑assurance measures, and best‑practice checkpoints to ensure high availability, scalability, security, and cost‑effectiveness of complex engineering projects.
This article explains how traditional, lengthy test‑strategy documents can be replaced by a concise, one‑page visual diagram that clearly presents what to test, how to test, guiding principles, and the roles of test left‑shift, test quadrants, test layers, and test right‑shift, using a real‑world example to illustrate the approach.
At the 2021 China Internet Test Development Conference, ZTO Technology’s senior architect Gong Linhua detailed how their thousand‑person team builds a robust quality assurance system through business testing, continuous innovation, specialized training, and precise metric‑driven management, aiming to accelerate delivery while maintaining high software quality.
This article examines the challenges faced by a search middle platform—such as inaccurate impact assessment, unstable underlying clusters, and missing process standards—and details a comprehensive quality‑assurance strategy that includes baseline test suites, stability practices, performance testing, emergency drills, and systematic monitoring to ensure reliable search services.
This article explains how to determine the right amount of testing for a software product by providing evaluation criteria, a step‑by‑step testing strategy—including recording processes, unit, integration and end‑to‑end tests—coverage types, tools, and how to incorporate field feedback for continuous improvement.
Xianyu tackled the high‑cost manual testing of its multi‑scenario transaction platform by implementing JVM‑sandbox traffic‑recording tools (Doom/Blizzard and Phoenix) for interface‑level replay, service‑oriented link testing, and shadow‑DB isolation, enabling automated end‑to‑end validation across dozens of applications and business modes.
This article details a comprehensive UI automation framework for the Dali Smart Homework Lamp, covering business context, product features, testing challenges, automated script generation, modular case design, multi-device coordination, error analysis, and future directions for intelligent UI validation.
This article identifies the most common obstacles teams face when adopting test automation—such as choosing approaches, selecting tools, managing data, and timing tests—and offers actionable solutions to help organizations implement effective, sustainable automation pipelines.
The article reviews four in‑depth talks from MTSC2021 Shanghai, detailing how ZTO, Meituan, ByteDance and Kujiale build large‑scale testing frameworks, event‑tracking QA, advertising system reliability, and multi‑dimensional online inspection to ensure product quality across complex business scenarios.
This article explains how test engineers can embed quality into software projects by contributing at the requirement, implementation, and organizational levels, turning testing into a strategic asset that enhances team collaboration, reduces rework, and drives continuous improvement.
This article outlines the essential concepts, four‑step workflow, and practical tips for beginners to define scope, choose tools, design frameworks, execute test cases, and generate effective automated testing reports.
At the 2021 QECon conference in Shenzhen, Zhongtong Express senior architect Wu Da detailed the design and evolution of their big data quality assurance framework, covering six key layers and highlighting future trends in predictive analytics and deep business integration.
The article explains how defect repair costs increase the later they are discovered, argues for shifting testing activities left into the requirement phase, describes three requirement granularities (Epic, Feature, Story) and outlines specific quality activities for each level to achieve early defect detection and lower overall development cost.
The article surveys five major software testing organization models—centralized, decentralized, hybrid, third‑party, and “no‑testing”—explaining their evolution, characteristics, advantages, and challenges, and discusses how agile practices and business needs drive the shift toward integrated or outsourced testing structures.
The article outlines how map‑collection vehicles achieve high hardware quality and reliability through systematic design, production management, and rigorous testing—including derated components, redundancy, thermal and mechanical safeguards, sensor protection, and data‑driven failure prediction—to meet MTBF targets and extend service life.
This article describes a Selenium‑based automated testing solution that randomly assembles ad landing page components, captures before‑and‑after screenshots, and evaluates visual similarity using histogram and dHash algorithms to ensure "what you see is what you get" across thousands of component combinations.
This article explains the fundamental concept of code coverage, its basic classifications, the various metrics such as function, line, branch, and condition coverage, factors that affect coverage, its significance for software quality, and practical ways to measure and improve it.
This article introduces JD's code coverage statistics platform, detailing its concepts, significance, implementation approaches for Android and iOS—including Jacoco and Xcode configurations—its SDKs, data collection, reporting mechanisms, and how it enhances testing quality and development efficiency.
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 article introduces Youzan's testing team, detailing its growth to over 120 engineers across three cities, the test‑development responsibilities, automation and load‑testing practices, quality‑assurance framework, training programs, and the open, growth‑focused team culture that candidates can expect.
This article explains how Zhongtong implemented a Java‑based code‑coverage service using Jacoco, integrated it into their CI pipeline, generated multi‑dimensional coverage reports, and refined testing workflows to improve software quality and reduce untested code.
Baidu’s Mini Program QA system uses AI‑driven automated traversal, page‑anomaly detection, and a scalable cloud‑phone cluster to scan hundreds of thousands of mini‑programs, identify red‑line issues via image, OCR and deep‑learning analysis, and automatically resolve most problems, boosting audit efficiency and user experience.
The article details Youku’s effort to build a test‑effectiveness evaluation system for its client by prioritizing data‑driven code‑coverage metrics, comparing JaCoCo with an internal tool, outlining the native class‑loading architecture, Python‑based analysis pipeline, achieved coverage insights, and plans to expand automation and visualization across modules.
This article compiles lessons from various engineering blogs on why and how to conduct code reviews, covering their role in quality assurance, team learning, pull‑request preparation, constructive communication, and the importance of praise and positive tone.
This article presents a comprehensive model quality assurance framework for click‑through‑rate (CTR) prediction, detailing the challenges of data and logic inconsistency, defining consistency goals, describing a full‑stack verification pipeline—including online data capture, offline sample alignment, multi‑stage q‑value comparison, and automated reporting—and sharing practical deployment experiences and results.
This article outlines Youku's end‑to‑end service‑side quality assurance framework, detailing the factors that affect quality across the development lifecycle, the automated testing practices integrated into the release pipeline, the platform capabilities built for data collection and replay, and the metrics used to measure improvements in reliability and development efficiency.
This article reviews key insights from the book “How Google Tests Software”, highlighting Google’s view that quality stems from integrated development and testing, describing the distinct roles of SWE, SET, and TE, and comparing these practices with typical domestic software testing structures.
DoKit’s one‑machine‑multi‑control lets an Android host device manage slave devices over a LAN without extra permissions or code intrusion, dramatically streamlining functional regression and compatibility testing while supporting user‑behavior recording, and is slated for open‑source release with future extensions to Flutter and Web.
This article explains why test cases are essential, outlines their purposes, presents key design principles and black‑box techniques, provides a web‑UI checklist example, describes basic test case components, and emphasizes the importance of thorough test case review.
This article compiles key lessons from various engineering blogs on why code reviews matter, covering their role in quality assurance, team growth, effective review checklists, preparing pull requests, humane communication, and recognizing contributions, providing a comprehensive guide to improve review processes.
This article compiles a wide-ranging discussion on how development teams can guarantee that developers allocate sufficient time for writing test cases despite tight schedules, covering division of testing duties, organizational processes, requirement handling, performance metrics, and skill development.
This article explains the multiple benefits of code review—from knowledge sharing and improving code quality to enforcing team standards—and provides practical steps, cultural tips, tool recommendations, and workflow guidelines to help development teams adopt effective code review practices.
This article outlines the most frequent obstacles teams encounter when adopting test automation—such as selecting appropriate methods and tools, managing massive test data, and timing automation phases—and provides practical strategies to address each challenge for more effective and reliable software quality assurance.
This article shares the front‑search team’s experience on how test engineers can shift testing left by actively participating in requirement and design reviews, outlining consensus building, SDLC context, review procedures, current challenges, implementation steps, achieved outcomes, and future outlook.
The article outlines why code coverage is valuable for developers, warns against chasing high percentages without quality, emphasizes risk‑based assessment of uncovered code, and provides practical guidelines for incrementally improving coverage, integrating it into reviews, and setting sensible thresholds.
This article chronicles Microsoft’s testing journey from the 1990s separate SDET and STE roles, through the early‑2000s consolidation of those roles, to the modern cloud‑native “combined engineering” model that reshapes quality responsibility, accelerates delivery, and introduces specialized virtual teams for performance and security.
This article explains how an online education quality team uses real user traffic to build a comprehensive platform that improves CI/CD maturity, automates testing, captures and replays traffic, and provides scalable services for continuous quality and efficiency across the entire development lifecycle.
Traditional testing suffers from low efficiency, unclear scope, and unquantifiable quality standards, especially in fast‑paced agile and microservice architectures; the article introduces a Precise Testing system that leverages bidirectional traceability, intelligent test case selection, incremental coverage analysis, and recommendation algorithms to make testing more accurate, automated, and data‑driven.
This guide outlines a comprehensive seven‑stage process—from planning and tool selection to environment setup, script design, execution, and result analysis—providing practical best‑practice notes to maximize test automation efficiency and coverage.
The article argues that the so‑called “shift‑left testing” is not a new concept but a rebranding of long‑standing testing principles, critiques its misinterpretation as moving test engineers left, and advocates for developers to own unit testing while professional testers focus on risk‑based, comprehensive quality assurance across the software lifecycle.
The article explains how a company can achieve a process‑oriented organization by defining business flow, aligning processes, leveraging IT to solidify data handling, integrating quality standards, and establishing continuous operations, emphasizing the need for clear concepts and roles across the enterprise.
This guide explains why many IT budgets neglect quality assurance, presents data from the 2019‑2020 World Quality Report, and offers practical steps—ownership, prioritization, integration, automation, reporting, and documentation—to establish a robust QA workflow even with limited resources.
Exception testing, a distinct testing type from functional and performance testing, helps uncover system issues caused by system, dependency, or application anomalies, enabling designers to improve solutions and enhance overall system stability through comprehensive test case design and execution.
Code reviews are essential for maintaining product quality, reducing technical debt, and fostering team knowledge sharing, yet they face challenges like time constraints and subjective biases; this guide outlines why reviews matter, their benefits, common pitfalls, formats, participants, focus areas, processes, key operations, principles, and typical issues with practical examples.
The talk explores the current pain points of AI testing, outlines data‑quality analysis methods, highlights critical ETL and model‑testing considerations, and shares practical case studies and platform designs to improve machine‑learning quality assurance.
This article analyzes Beike's massive real‑estate ecosystem, detailing the intricate business flows, technical architecture, and quality‑assurance challenges, and explains how a suite of internal platforms—KeTest, KeOnes, sosotest, KeDiff, KePTS, and KeMTC—are engineered to deliver high‑performance, highly available services at scale.
This article analyzes the challenges of fragmented, high‑volume demand in a trading platform’s QA process and describes how introducing a tiered “no‑test” policy, white‑list and data‑driven operations, and rapid‑response procedures significantly boosted delivery efficiency and raised developers’ quality awareness.
This article explains the concept of test coverage, describes various coverage techniques such as statement, branch, path, condition, and boundary-value coverage, outlines key metrics, provides a practical coverage matrix example, and offers actionable tips for improving overall software testing quality.
This article outlines 13 practical code‑review standards that help improve software health, ensure quality, foster collaboration, and keep development teams satisfied by focusing on incremental improvements, timely feedback, education, and respectful communication.
This article describes how a commercial advertising team transformed manual ad‑recall testing into a semi‑automated regression workflow by building comparison, log, result, and case tools, addressing challenges such as anti‑fraud restrictions, data quality, special scenarios, and inter‑case interference.
The article explains how a quality management plan serves as a formal blueprint to identify user needs, define standards, assign responsibilities, select tools, and continuously control processes, ultimately ensuring customer satisfaction and business success.
The author recounts bugs uncovered during a web‑based QA session—ranging from mismatched character‑length limits and inconsistent filter defaults to fragmented documentation—highlighting how overlooking tiny validation rules can cause costly defects and why unified standards and professional testing are essential.
This article describes how our team designed and implemented a comprehensive online monitoring system for construction drawing generation, covering business background, technical architecture analysis, metric definition, monitoring methods, and the resulting dashboards that improve quality, stability, and rapid issue resolution.
The article uses a whimsical conversation between a developer and a testing deity to explore why testing is essential, how it functions as sampling, the limits of defect detection, and practical strategies such as TDD, continuous integration, and requirement control to improve software quality.
This guide walks you through the complete software testing lifecycle—covering requirement collection, test strategy, test planning, execution, pre‑release checks, and final release best practices—to ensure high‑quality, reliable software delivery.
Software testing is increasingly rapid and automated, yet testers often fall prey to cognitive biases—such as similarity, consistency, confirmation, conformity, inattention, and negativity—that cause missed defects; understanding and countering these biases can markedly improve test coverage and product quality.
This article explains the true purpose of code review beyond bug hunting, explores its cultural and quality benefits, and offers seven actionable recommendations—including small batch reviews, frequent cycles, choosing the right reviewers, rapid feedback, modern tools, pair programming, and blending online with offline sessions—to make code reviews more effective.
This article describes the design, implementation, and operational strategy of a comprehensive code‑metrics platform that standardizes coding standards, automates quality checks, and drives data‑guided improvements across multiple development teams, ultimately enhancing code reliability, maintainability, and CI/CD flow.
This article outlines a comprehensive roadmap for establishing a test automation framework, highlights key aspects such as exploratory testing, user experience, accessibility, dynamic content, and offers best practices for test case design, handling slow or failing tests, and maintaining reliable automated suites.
This guide explains why companies outsource software testing, outlines key factors such as outsourcing models, geographic location, service agreements, flexibility, and quality improvement, and provides a step‑by‑step process for investigating, interacting with, and selecting the right testing service provider.
The article explains the distinct purposes and benefits of performance, stress, and load testing, showing how each practice helps identify bottlenecks, ensure stability under load, and improve overall software quality throughout the development lifecycle.
This article outlines practical quality assurance strategies—including outsourcing QA teams, integrating testing early in the development lifecycle, and adopting automation frameworks—to improve software quality, reduce costs, and support business growth in digital transformation initiatives.
This article explains how Alibaba's search, recommendation, and advertising platforms handle the unique quality challenges of big‑data AI applications, detailing six major testing problems and the comprehensive strategies—including functional, real‑time, performance, and stability testing—used to ensure reliable online services.
The article outlines the essential technical and non‑technical competencies—communication, problem‑solving, data analysis, adaptability, prioritization, time management, programming basics, negotiation, mentorship, and strategic intervention—that enable a test manager to lead agile QA teams successfully.
The article outlines the Sigma Quality Management Platform’s event management journey across three development stages—establishing basic standards, expanding processes and channels, and achieving mature, integrated governance—while highlighting current challenges, continuous standard refinement, efficiency gains, and practical implementation details.
This article outlines Youku’s end‑to‑end quality assurance framework, detailing how the company tackles fast product cycles, complex playback verification, and device fragmentation through a platform‑based, offline‑online system that boosts development efficiency and delivers reliable user experiences across its services.
This article outlines a DevOps‑inspired metric system for front‑end projects, describing the five development stages—design, development, personal verification, version verification, and online verification—and proposing concrete, automatable indicators to help leaders assess and improve delivery quality and speed.
