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.
This article presents a curated list of fifteen essential books for software testers, covering foundational testing concepts, agile testing principles, practical BDD approaches, and DevOps methodologies, each accompanied by concise recommendation reasons to guide both beginners and experienced professionals.
To ensure stability and precision of Alibaba Youku’s massive video‑search platform, a three‑layer quality‑assurance framework was built—covering engineering regression and functional/effect monitoring, algorithmic data, UDF, feature‑column and index testing, effect baselines and impact assessment, plus user‑experience bad‑case mining and public‑opinion feedback loops.
This article reflects on the quality assurance challenges and solutions of the large‑scale CloudMap redesign project, covering core difficulties, QA responsibilities, testing strategies, performance monitoring, and post‑release optimization to ensure stable delivery for thousands of users.
This article examines the key differences between manual and automated testing, covering time cost, acceptance testing, accuracy, regression testing, and project characteristics to help teams decide which approach best fits their software projects.
During the pandemic, Tencent Cloud University partnered with its TVP team to launch a free live course series led by senior DELL EMC architect Ru Bingsheng, teaching disruptive, agile software‑testing innovations for the UVCA era, while offering interactive Q&A, prizes, and TVP certification information.
By unifying algorithm development, engineering, and a serverless gateway, the platform creates a stateless, automated pipeline that lets Python‑based services be deployed instantly, supports rapid low‑traffic iteration, scales with high‑performance runtimes, and ensures quality through automated testing, accelerating business evolution from startup to mature stages.
The article outlines essential software testing practices, emphasizing comprehensive business understanding, thorough process knowledge, early and prioritized testing, collaborative test case reviews, post‑test summarization, responsibility, and the benefits of automation to improve quality and efficiency.
This page compiles a comprehensive collection of Chinese-language articles and resources covering software testing principles, automation strategies, DevOps integration, QA best practices, and related development topics, providing readers with curated links to deepen their understanding of testing methodologies and industry trends.
Integration testing verifies that individually tested software units work together as intended, bridging the gap between unit tests and system tests, and is a critical practice for DevOps teams to ensure cohesive, reliable applications.
The article explains how well‑crafted test cases—containing precise names, IDs, preconditions, steps, data, expected results, actual results, and defect links—reduce reliance on individual testers, aid defect reproduction, support automation, serve as training material, and act as long‑term evidence while warning against over‑detailing in time‑critical or ad‑hoc scenarios.
This article explains the purpose of unit testing, outlines best‑practice guidelines for creating and managing unit test plans, and provides a comprehensive checklist covering input validation, date and time verification, security, usability, logging, business logic, reporting, environment, email, and search functionality.
The article describes how JD's mobile testing team created a component‑based "use‑case meta" framework that abstracts common test scenarios into six reusable categories, integrates them into the testing platform, and dramatically improves coverage, efficiency, and knowledge reuse across large‑scale app releases.
The QA team delivered a seamless, globally stable Double 11 “Cat Night” live stream across three apps and dozens of devices by applying client‑ and server‑side stability measures, international latency simulation, IPv6 support, cost‑effective CDN strategies, full‑chain monitoring, and automated asset‑loss safeguards, achieving zero financial loss.
The article outlines practical criteria for choosing which test cases to automate, emphasizing repeatability, difficulty, core workflow importance, extensive data requirements, risk assessment, and the value of regression, smoke, and sanity testing to improve software quality and reduce testing costs.
This article explains what APIs and API testing are, outlines various test case types and testing methods, compares API testing with unit testing, lists best practices, common error types, recommended tools, and challenges faced when testing APIs in software development.
On December 7, Youzan’s Mobile Technology Salon gathered over 100 participants and six speakers to showcase the company’s quality‑and‑efficiency initiatives, including a mobile basic guarantee system and code‑coverage‑driven testing practices, with session videos released, full PPTs available, and a follow‑up PaaS meetup announced for December 21.
Effective software testing is essential for SaaS startups to avoid costly failures; this guide outlines five key strategies—aligning quality checks with business goals, detailed test planning, fostering a supportive testing environment, conducting user acceptance testing, and measuring code quality with CISQ metrics—to ensure high‑quality releases.
Exploratory testing, a flexible, unscripted approach integral to agile development, enables rapid discovery of defects, improves user experience, and complements automated regression testing, while its various types, benefits, challenges, and common myths are examined to guide teams in effective implementation.
The article explains the distinction between automated testing and test automation, why test automation is crucial for continuous testing in DevOps pipelines, and outlines practical steps and tools needed to implement effective test automation for maintaining quality and speed in modern software delivery.
The article explains the distinction between automated testing and test automation, highlights why test automation is essential for continuous testing and DevOps pipelines, and outlines practical steps and requirements for implementing effective test automation in modern software delivery processes.
This article explores the evolution of software testing, the challenges posed by rapid internet-driven development, a six‑level model of AI‑augmented testing, practical application scenarios such as unit, API and UI testing, and a survey of leading AI‑powered testing tools shaping the future of quality assurance.
This article provides a comprehensive overview of the many functional and non‑functional software testing types, explaining their purposes, advantages, and typical usage throughout the testing lifecycle.
The article explains the benefits and limitations of test automation, outlines scenarios where manual testing remains essential, and provides practical guidance on deciding what to automate, why to automate, and how to implement automation effectively.
JD.com's Retail Technology and Data Platform orchestrated a full‑chain, four‑entry‑point stress test for the 11.11 shopping festival, introduced an upgraded Forcebot traffic‑recording tool, and implemented a "Quality Month" with ten safeguards to ensure system stability and prevent incidents during the massive sales event.
This article explores common pitfalls in defining technical testing KPIs, distinguishes between platform‑integration and atomic‑capability goals, and provides a step‑by‑step framework for aligning objectives, metrics, and implementation plans to drive measurable quality improvements.
This guide presents fifteen practical strategies for writing effective test cases, covering domain knowledge, step decomposition, pre‑conditions, documentation, data handling, organization, naming conventions, customer focus, coverage, reuse, and maintenance to boost testing efficiency and quality.
This article introduces a software testing experience map that divides testing hard skills into three major areas—requirement quality, test quality, and release quality—explaining why each is essential, how testers can ensure them, and offering practical guidance on smoke testing, test planning, test cases, and release monitoring.
iQIYI tackled the complexity of its large, multi‑team, multi‑technology mobile app by implementing an automated, standardized logging and diagnostic platform—including UI testing, code‑coverage, a unified SDK, real‑time log debugger and web viewer—enabling proactive design‑for‑debug, faster releases and higher quality.
The article examines Alipay's mobile DevOps implementation, contrasting it with web DevOps, outlining development stages, highlighting technical and operational challenges such as fragmented device ecosystems, quality assurance, continuous integration, and the impact of emerging technologies on the mobile development workflow.
This article explains the importance of requirement analysis in software testing, outlines its necessity, consequences of neglect, and provides a step-by-step guide on how to perform effective requirement analysis to improve test scope, priority, and overall quality.
This article explains why evaluating test case effectiveness matters, defines effectiveness as the ratio of discovered bugs to total bugs, and introduces mutation testing with a fully automated robot that injects bugs, runs tests, compares results, and reports a quantitative effectiveness score.
The article explains what requirement analysis is, why it is essential for successful testing projects, outlines a step‑by‑step approach to performing it, and offers practical tips for improving analysts' skills, emphasizing business knowledge, user perspective, continuous learning, and proactive collaboration.
The article outlines a complete testing framework for advertising recall services, analyzing three demand types, defining testing focus for each, and presenting tools for log comparison, recall result verification, result comparison, and batch regression to ensure high‑quality ad delivery and revenue stability.
The article outlines seventeen essential and practical skills for software testers, ranging from rational clarity and staying updated on technology trends to effective planning, cross‑browser testing, front‑end communication, continuous learning, collaboration, and mastery of testing tools.
This article translates Google's engineering practices on code review, outlining the purpose, principles, guidelines, and detailed steps for reviewers and authors to ensure high code quality, efficient collaboration, and continuous improvement across design, testing, documentation, and review speed.
This comprehensive guide explains Google's code review standards, covering reviewer responsibilities, design principles, conflict resolution, what to examine in a change list, review speed, handling large changes, and effective comment writing to ensure high code quality and team productivity.
This article explains why code review is essential for software teams, covering its benefits for knowledge sharing, code quality, and team standards, and provides practical guidelines on making code review a mandatory step, fostering a review culture, and applying effective techniques and tools.
Interviews with 14 IT experts reveal that slow adoption, skill shortages, costly manual processes, and insufficient organizational support hinder automated testing, while opportunities exist through better tooling, containerization, and focused training to improve ROI and software quality.
This article explains the multiple benefits of code review—including knowledge sharing, improved code quality, and enforcing team standards—and provides practical steps, cultural tips, and tool recommendations to make code review a mandatory, effective part of any development workflow.
This article presents a comprehensive 18‑point checklist covering smoke testing, installation/uninstallation, upgrade methods, business functionality, stability, performance, interface testing, usability, device compatibility, platform integration, special scenarios, permissions, security, data protection, phone features, competitor comparison, common oversights, and feedback channel establishment for mobile app testing engineers.
This article details MaFengWo's travel‑booking team's end‑to‑end quality‑system construction, covering common QA misconceptions, project‑process control, comprehensive business testing, online issue closure, and tool development to achieve faster delivery, fewer bugs, and higher system stability.
This article explains how to transform product requirements into clear, executable test cases by defining unique conditions and deterministic results, discusses typical questions about coverage and edge cases, and provides concrete examples from game‑account and book‑purchase scenarios to illustrate effective case design.
JD Zhizhi's Wise Open Platform introduces innovative technology and platform models to enhance AI data annotation efficiency, security, and trust between clients and annotation teams.
This article outlines nine essential qualities and habits—such as curiosity, troubleshooting skill, perseverance, creativity, perfectionism, technical knowledge, confidence, persuasion, and programming background—that together form the roadmap for anyone aspiring to excel as a software test engineer.
The article explains the importance of bug analysis for improving product quality, outlines the information that can be analyzed, describes common bug resolution categories, discusses bug severity levels, and shows how various stakeholders can use bug metrics to drive process optimization and predict future issues.
This guide outlines a comprehensive software testing framework, covering basic smoke tests, functional, security, interface, compatibility, installation, performance, regression, and advanced testing practices, with detailed steps, responsibilities, and reporting requirements for development, testing, and product teams.
This comprehensive guide outlines 40 essential project management terms—from basic concepts like project plans and WBS to advanced topics such as risk mitigation, Kanban flow limits, and quality assurance—helping professionals enhance their terminology and improve project communication.
This article explains common misconceptions about test automation, why it requires ongoing maintenance and human expertise, how to balance automated and manual testing, identifies key areas to automate using risk‑based, conversation‑driven, and exploratory approaches, and discusses how to evaluate the true value of automation.
The article analyzes the Pinduoduo coupon vulnerability, explains its logical and programmatic roots, discusses why rapid iteration often sacrifices quality, and suggests applying solid software‑engineering quality‑assurance practices to prevent similar large‑scale losses in e‑commerce products.
This article expands on functional testing by exploring three key control areas—product knowledge, development quality through version control and test case integration, and environment configuration—offering practical insights and best practices for testers to enhance test effectiveness and drive project quality.
This comprehensive guide explains the most common software testing types—from Alpha and Beta to Security, Load, and Compatibility testing—detailing their purposes, execution contexts, and how they help ensure software quality before release.
This article details the architectural design and engineering practices behind building a comprehensive Application Performance Management dashboard for Android applications, covering real-time monitoring, version comparison, development cycle tracking, automated data collection, and integrated test coverage analysis to ensure sustainable software quality and delivery efficiency.
This article explains how Alibaba built a comprehensive Blink testing platform—including code‑quality checks, functional, performance, stability, and pre‑release testing—to ensure the reliability and scalability of its real‑time big‑data processing engine during massive workloads like Double 11.
The article analyzes how Google responded to a testing crisis by empowering a visionary leader, establishing supportive structures, encouraging innovation, and persisting over years to embed a quality‑centric culture that eventually led to decentralized testing, SRE adoption, and a shift toward test‑design engineers.
The article explains JD's high standards for software reliability, describes the testing team's shift toward test development, outlines core software testing concepts, standards, and the distinction between testing and quality assurance, while also promoting a free copy of the related book.
The article examines the background, challenges, and outcomes of research‑test integration at UC International, analyzes the evolution and current concerns of software testing careers, and offers insights on future testing roles, good‑enough practices, and recommendations for test engineers.
The second Hangzhou Testing Salon, organized by Youzan with partners KuJiaLe, Mogujie and 51 Credit Card, gathered over 300 attendees from 130 companies to share practical insights on full‑chain performance testing, a distributed pressure‑testing engine, rule‑based quality platforms, front‑end coverage tools, search‑service reliability and data‑quality monitoring.
The article details the structure, daily responsibilities, quality‑assurance processes, automation strategies, tool development, performance testing, and quality‑culture initiatives of the Shanghai testing team at Dada‑JD.com, illustrating how systematic testing and DevOps practices enhance product stability and development efficiency.
A project manager reflects on a four‑month development effort that collapsed after launch, analyzing mistakes in quality control, trust, ownership, requirement handling, and code review, and shares concrete steps taken to fix the issues and key lessons learned for future projects.
This article provides a comprehensive overview of the daily work of the Shanghai R&D Center Test Team at Dada-Jingdong to Home, covering project quality assurance, automation, tool construction, and quality culture building.
The article explains the concept of closed‑loop thinking, illustrates how it can be applied to software testing through a concrete bug‑handling example, and shows how systematic feedback and reflection improve testing efficiency, knowledge reuse, and personal skill growth.
This article examines common software testing antipatterns, explains why testing the wrong functionality and over‑focusing on code coverage are misguided, introduces a mental model for prioritizing critical, core, and other code, and presents practical metrics and guidelines for effective, behavior‑driven testing.
This article expands on common software testing antipatterns, explaining why testing the wrong functionality, focusing on internal implementation, and obsessing over code‑coverage percentages can waste effort, and it introduces a mental model, practical metrics, and guidelines for writing effective, business‑oriented tests.
A senior project manager reflects on a four‑month, 100‑person‑day software project that collapsed after launch, analyzing five critical mistakes—from neglecting quality and over‑trusting the team to lacking ownership, design, and code review—and shares the concrete steps taken to rescue the product and the key takeaways for future projects.
This article examines the importance of code review in fast‑growing development teams, discusses its benefits and common challenges, and provides practical guidelines—including review frequency, time limits, checklists, and cultural tips—to help engineers improve code quality and collaboration.
Google’s test engineers (TEs) act as the glue between product, development, UX, and release teams, using automated testing, performance checks, and quality standards to ensure rapid, reliable product releases, while also tackling challenges such as battery usage tracking, data set evaluation, and accessibility consulting.
The article argues that testers should abandon a passive, isolated role and become proactive quality guardians who understand business, design logic, and user scenarios, using testing as a project‑management lubricant to drive continuous improvement and build a strong capability barrier.
This article outlines the comprehensive responsibilities of a software testing engineer, covering requirement review, documentation, system architecture awareness, process management, risk and time management, and provides practical guidelines to improve software quality and delivery speed.
This article outlines the essential knowledge for software test engineers, covering the defect lifecycle, status definitions, role responsibilities, defect management procedures, test case design standards, submission guidelines, priority and severity classifications, and practical tips for applying these concepts in real projects.
The article shares a test engineer's seven‑year journey, describing how their understanding of testing has evolved through four stages, outlining the broader responsibilities of test engineers, and offering practical advice on improving product quality, fostering collaboration, and ensuring technical solutions are effectively adopted.
This article offers nineteen practical pieces of advice—from empathizing with users and reading bugs to mastering automation and continuous learning—to help both novice and experienced software testers improve their skills and impact.
The article shares a test engineer’s seven‑year journey, highlighting four pivotal shifts in testing practice, redefining the engineer’s duties toward helping projects improve quality, quantifying quality metrics, and continuously refining tools and processes to enhance overall product reliability.
This article presents a detailed mobile testing automation solution covering quality assurance, early test involvement, systematic automation processes, benefit measurement, and team development to improve product quality and testing efficiency across the entire software lifecycle.
By applying a PDCA‑based quality‑operation framework that aligns QA KPIs, drills defect data across dimensions, automates test‑gate checks, and drives continuous improvement actions, Meituan Dianping’s Intelligent Payment team reduced severe defect ratios, met defined metric targets, and boosted iteration efficiency while supporting rapid business growth.
The Jingdong Woodpecker system is an automated monitoring solution that scans tens of thousands of e-commerce activities daily across multiple platforms, detecting functional and performance issues to ensure optimal user experience and prevent revenue loss.
The article outlines the comprehensive technical knowledge, testing fundamentals, business understanding, tool proficiency, coding ability, and communication skills required to be considered a senior test engineer, emphasizing industry experience, test process mastery, and continuous learning.
The article explains how QA engineers can systematically measure, analyze, and resolve app slowness by quantifying response times, dissecting device fragmentation, network latency, and backend complexity, and establishing a data‑driven quality loop to improve user experience.
This article describes how Qunar built a comprehensive automated testing system triggered by beta releases, incorporating CI‑driven execution, strong release‑blocking controls, and multi‑channel result notifications to improve release quality, reduce manual effort, and close testing gaps in a fast‑moving internet environment.
This article highlights frequently ignored testing problems such as browser navigation affecting data integrity, unnoticed JavaScript errors, boundary value issues in UI components, backend code review importance, improper handling of zero versus empty values, timestamp misuse, and inadequate validation of varchar and text fields, emphasizing meticulous testing for high‑quality software delivery.
The article presents Zhang Qi's insights on end‑to‑end quality assurance for JD's POP platform and 7FRESH stores, covering pre‑, during‑, and post‑release testing measures, big‑data‑driven automation, tester roles, team growth strategies, and knowledge‑sharing initiatives.
The article introduces Smart, a platform that records manual API testing actions and database interactions to automatically generate and execute API test cases, addressing data preparation, environment setup, and case authoring challenges while detailing its architecture, implementation, and future improvements.
Test Fest is a company‑wide, short‑duration crowdsourced testing event that brings product managers, developers, designers, operations, and support staff together to explore a product, uncover bugs, improve compatibility, and generate actionable insights, dramatically boosting testing efficiency and ROI.
The article outlines sixteen key characteristics—including a skeptical attitude, uncompromising quality, user‑centric thinking, early testing, risk management, strong analysis, negative testing, effective negotiation, and teamwork—that together define what makes a software tester truly outstanding.
