This article summarizes Yegor Bugayenko’s “Quality Wall to Protect Developers Against Stress and Fear,” explaining how automated quality gates, testing, static analysis, and disciplined merge processes can reduce bugs, lower developer anxiety, and enable faster, safer code delivery.
This article explains how shifting QA left with agile testing, automation, continuous integration, and AI-driven approaches can catch bugs early, improve user experience, reduce costs, and ensure higher software quality throughout the development lifecycle.
This article explains why a quality‑score model was created, reviews industry quality‑measurement practices, describes how key indicators were selected and weighted, outlines the calculation formula, and shares the implementation approach and observed benefits for improving product quality and risk control.
AWS CodeGuru, an AI‑driven code review service, automatically analyzes code in GitHub or Bitbucket, offers performance and error suggestions, and helps large teams maintain high‑quality software without the overhead of manual reviews.
This article explains why API testing has become essential in modern agile and IoT‑driven development, outlines the API testing pyramid, covers HTTP and REST fundamentals, and provides practical guidance on selecting tools, creating functional and load tests, and ensuring early, rapid feedback.
This article explores the challenges of interface testing for a large-scale home‑decoration platform, detailing pain points, testing stages, practical tips, and real‑world case studies to help backend engineers design effective, automated API tests for complex custom data.
This article explains how adopting continuous testing—by decentralizing test teams, clearly defining test types, and managing automated test data—enables faster feedback, higher quality releases, and smoother DevOps adoption, while highlighting practical steps and common pitfalls.
This article outlines six frequent code review pitfalls—including missing change notes, overusing generic exception handling, blind trust in third‑party inputs, overly broad variable scopes, lack of staged results, and excessive logging—and offers practical recommendations to improve code quality and maintainability.
QAOps integrates continuous testing from DevOps into the software development lifecycle, combining automated testing, parallel execution, and scalable reporting to improve collaboration between QA engineers, developers, and operations teams while accelerating and stabilizing software releases.
The article explores how disciplined Code Review fosters better software quality, emphasizing that every line of code should have purpose, encouraging concise, well‑named, and well‑documented code, while highlighting common pitfalls such as unnecessary complexity, poor exception handling, and scattered constants.
The article outlines why end-to-end test automation often fails—such as hiring the wrong people, neglecting code quality, underestimating long-term effort, misunderstanding automation scope, limited test coverage, and poor visibility—and offers practical guidance to improve automation success.
Load testing, which simulates thousands of real users, is crucial for uncovering performance bottlenecks that functional tests miss, and integrating automated load tests into every CI cycle helps prevent crashes, protect revenue, and ensure reliable software delivery.
This article explains the fundamentals of unit testing, covering its definition, core concepts, essential principles, practical techniques such as mocking, and its role in test automation and continuous integration within modern agile development.
This article examines common pitfalls of test automation, critiques traditional framework‑only solutions, and details how the HAWK platform integrates automation frameworks, case‑set management, and a data factory with CI/CD to boost testing efficiency and product quality.
This article provides a comprehensive Q&A covering common misconceptions, recommended books, incremental vs. iterative development, test‑to‑dev ratios, suitable projects, DevOps differences, unit‑test ownership, workload estimation, bug handling, release criteria, test‑team organization, automation practices, and essential skills for effective agile testing.
The article explains how to use feature flags in a three‑tier microservice architecture, describing the need for both high‑level end‑to‑end tests and low‑level unit tests within CI/CD pipelines to ensure correct behavior when flags are on or off, while avoiding excessive test combinatorial explosion.
This article compiles practical guidelines for software testers, covering comprehensive business understanding, end‑to‑end workflow awareness, common developer pitfalls, early testing of new features, prioritizing complex requirements, verification and negative testing, test case preparation, post‑test reviews, responsibility, and the benefits of test automation.
This article explains why code review is essential for improving code quality, fostering team knowledge sharing, enforcing standards, and reducing technical debt, and provides concrete guidelines on making code review a mandatory, cultural part of the development workflow with practical tips and tool recommendations.
This article explains the importance of continuous integration for maintaining code quality in enterprise development, defines CI and its core principles, and reviews several popular free open‑source CI tools—including Travis CI, Jenkins, Circle CI, and Drone CI—providing brief usage insights and project links.
The article outlines the advantages of automated testing—including 24/7 execution, efficient regression, reusability, time and cost savings, early defect detection, reduced manual effort, increased coverage, and monitoring—while acknowledging its limitations and the continued need for manual testing.
This guide outlines common tester‑developer interaction scenarios, highlights typical mistakes, and provides step‑by‑step best‑practice responses to improve bug reporting, collaboration, and overall software quality assurance processes.
This article outlines a step‑by‑step approach for identifying change opportunities, persuading leaders to prioritize software quality, and sustaining effective transformation through audience insight, problem framing, tone crafting, and collaborative ownership, helping teams accelerate market delivery.
This article explains the end‑to‑end process of designing, implementing, and visualizing a quality‑measurement system that aggregates department, application, and individual data, defines evaluation methods, and uses offline Hive calculations to deliver fast, flexible dashboards for software quality improvement.
Based on interviews with 31 executives from 27 companies, this article reveals over a dozen concrete advantages of automated testing—ranging from time and cost savings to enhanced coverage, security, and faster releases—across multiple sectors such as finance, healthcare, automotive, and telecom.
The article examines the frequent reasons test automation projects collapse—from unrealistic 100% automation expectations and poor management visibility to inadequate manual testing, tool mis‑selection, false positives, and lack of collaboration—offering practical guidance to improve automation success.
This article outlines the six-stage automated testing lifecycle methodology—from defining automation scope and selecting tools, through test planning, environment setup, script development, execution, and result analysis—providing practical guidance for improving software quality with efficient, resource‑conscious testing practices.
The Ctrip Technology Salon gathered over 250 experts and practitioners from Ctrip, Huawei, NetEase and others to discuss how AI, automated testing platforms, DevOps, and natural‑language testing frameworks can dramatically improve test engineering efficiency and software quality.
This article explains the importance of code review for improving software quality, outlines the benefits of using Gerrit as a CR tool, describes the detailed workflow and promotion strategies, and discusses future extensions such as CI integration, issue tracking, and metric‑driven improvements.
The article explains how shifting from fragile GUI‑level testing to automated API testing improves reliability, speed, and coverage in agile development, offering concrete strategies, examples, and tool recommendations for integrating API contracts into continuous integration pipelines.
To meet strict quality goals for iOS projects, the article describes adopting intermediate‑file code‑coverage instrumentation, generating gcno/gcda files, using lcov for full and incremental analysis, and integrating the process into builds and CI to enforce coverage thresholds and guide test‑case design.
This article explains why most test failures stem from environmental or procedural issues rather than real defects and introduces a methodological framework—Frequency, Isolation, and Disposable environments—to systematically improve test stability, reduce noise, and accelerate defect detection.
Based on interviews with 31 senior executives from 27 companies, this article identifies the most common obstacles to automated testing—including entrenched corporate culture, fragile test infrastructure, poor communication, manual testing mindsets, inadequate reporting, and integration challenges—highlighting how these factors impede test automation progress.
The article humorously explains that the true goal of unit testing is to ensure software quality while maintaining development speed, comparing ineffective testing to practicing shooting without scoring, and suggesting that without proper practice, both efforts may be futile.
The article argues that investing in internal software quality—clean architecture, low technical debt, and well‑structured code—lowers long‑term development costs and speeds up feature delivery, contradicting the common belief that higher quality always means higher expense.
Microsoft’s Azure DevOps team dramatically improved engineering efficiency by adopting a shift‑left testing strategy, replacing thousands of legacy functional tests with fast, reliable unit and integration tests, establishing six testing principles, a tiered test pyramid, and data‑driven metrics that now enable tens of thousands of daily releases.
This article offers a practical, experience‑based overview of unit testing, explaining why it matters, what makes a good test, when to write or skip tests, who should write them, and how to structure them effectively for reliable software quality.
This article introduces a layered testing methodology that separates presentation, core, and foundation layers, explains test case specifications and naming conventions, provides Java code examples for atomic, basic, and framework layers, and discusses optimization techniques such as data construction, regression testing, and exception validation to improve automation efficiency.
The article examines why test coverage matters, how Google and Facebook approach automated testing, the cultural emphasis on code ownership, and the practical limits of achieving 100% coverage in large-scale software projects.
The article explores how unpredictable black‑swan events, the butterfly effect, Murphy's law, rapid business growth, technical debt, tool choices, complex domains, documentation, and leadership all combine to threaten software stability, and proposes agile, systematic, and quality‑centric approaches to mitigate these risks.
This article shares practical experiences from unit testing a 6000‑line C module, detailing static code review and dynamic gtest testing, uncovering common defects such as memory leaks, and presenting two memory‑leak case studies with root‑cause analysis and cleanup recommendations.
The article examines the common friction between testers and developers, likening it to the Prisoner's Dilemma, identifies typical sources of conflict such as unclear processes, standards, resource contention, and attitudes, and offers five practical strategies to improve communication, workflow, and teamwork for better software quality.
The article explores how to deepen functional testing through horizontal expansion by focusing on product knowledge, development quality control, and environment configuration, offering practical guidance on version control, test case integration, database and configuration management, and the critical role of logs.
This article explains SonarQube's main components—including server processes, database, plugins, and scanners—and describes the end‑to‑end workflow that integrates code analysis into development, CI/CD pipelines, reporting, and operational monitoring.
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.
This article provides a comprehensive testing guideline covering test planning, test design, bug submission and tracking, regression testing scope determination, and internal communication practices to improve software quality and testing efficiency.
The article argues that over‑emphasizing business at the expense of technology harms system robustness, proposes quantifying technical KPIs across business, technical, and team contributions, and offers concrete metrics and examples to help engineering leaders restore a tech‑focused culture.
The article discusses how embracing speed and flexible configuration in QA, exemplified by the Beetle platform’s interface testing workflow, can improve project efficiency, enable unified automated testing, and integrate continuous integration, while emphasizing that tools alone cannot guarantee test quality.
The article details JD Logistics’ quality department’s evolution of its automated testing platform, Linglong, describing the business background, limitations of the previous system, the new architecture, core functionalities such as task scheduling, multi‑task execution, data‑driven testing, and future development plans.
This article describes how a hotel testing team integrated white‑box testing—code review and static analysis—into fast‑paced agile workflows, detailing the exploration timeline, typical functional testing challenges, three concrete bug‑finding case studies, measurable quality improvements, and practical promotion guidelines.
This article explains the concept, measurement dimensions, and practical issues of code coverage, compares full and differential coverage, describes JaCoCo's on‑the‑fly and offline instrumentation techniques, and outlines how to resolve instrumentation conflicts in a Java service environment.
This article reviews the six‑year evolution of Baidu's system‑level testing technology, describing how the testing approach progressed from manual testing through automated scripts, platform integration, cloud‑based testing, and finally a modular, service‑oriented testing platform to support large‑scale continuous integration.
This article shares practical experiences from unit testing a critical C module, describing common memory‑leak scenarios, their root causes, and concrete solutions while also offering a checklist of typical leak‑prone patterns for developers.
Continuous Integration (CI) is a DevOps practice where developers frequently merge code into a shared repository, triggering automated builds and tests to quickly detect defects, improve software quality, and accelerate delivery, while fostering a culture of frequent integration and reducing manual release effort.
This article presents a concise collection of Java backend code‑review best practices—ranging from parameter validation and null‑safety to logging, thread safety, and design simplicity—offering actionable tips to improve code quality and avoid common pitfalls.
This article shares an Alibaba technical expert’s data‑driven case study on improving a software development team’s efficiency and quality through agile practices, detailed metric analysis, targeted solutions, and continuous data operations, demonstrating how systematic measurement can reduce overtime and create a virtuous development cycle.
This article explores how project management’s cost‑schedule‑quality triangle, ISO quality definitions, the software quality “iron triangle” of process, organization, and technology, and the six quality characteristics guide developers and testers in improving product quality through systematic thinking and practical testing methods.
Parallel testing overlaps development and testing to dramatically shorten delivery cycles, shift quality checks earlier, and improve overall software quality, while the supply‑chain case study shows layered testing, automated interface tests, CI pipelines, and practical tips for stable automation and low‑coupling design.
Over the past four years a company that adopted fifteen automation‑testing principles from scratch achieved 100% API test coverage across five product lines, stable weekly releases, market leadership in two segments, and rapid expansion into three new product areas, demonstrating the lasting impact of disciplined test automation.
This article explains what APIs are, why functional API testing is essential, outlines the test pyramid, discusses the advantages of API tests such as higher coverage and faster feedback, and provides practical guidance on tools, test design, and CI integration.
This article explains the importance of problem localization for testers, outlines a systematic approach from user interface to database, and provides practical step‑by‑step techniques, case studies, and tips to improve bug detection, communication, and overall software quality.
The article introduces ARES, a module-level automated regression testing system that records real online data, replays it offline as a black-box test, and provides low-cost deployment, full automation, high coverage, and detailed reporting to simplify testing of complex backend services.
The article examines how rapid mobile internet growth reshapes software quality expectations, urging QA engineers to balance bug prevention, end‑to‑end service reliability, and user‑centric product excellence across evolving B2C scenarios.
The article examines various viewpoints on product quality, critiques common misconceptions about warranties and consumer expectations, presents formal definitions from Wikipedia and business dictionaries, and reflects on how quality management integrates meeting requirements, standards, and continuous improvement in both software and broader industries.
