This article explains the definitions, objectives, importance, and types of stability and reliability testing in software development, highlighting how these tests improve system availability, reduce failure risk, and guide corrective actions to lower maintenance costs.
The article examines why software testing inevitably consumes time and resources, explains the limits of both manual and automated testing, outlines scenarios best suited for automation such as regression and performance testing, and warns against unrealistic expectations, unnecessary tests, and security blind spots.
The article details how CITIC Bank’s software development center created a digital testing quality‑control “control cabin” that visualizes business rules, data links, execution results and performance risks, enabling automated, AI‑assisted testing and comprehensive risk monitoring across its entire financial services ecosystem.
This article traces the evolution of software testing from manual QA to developer‑driven automation, explains what unit testing is, presents the testing pyramid, outlines its many benefits, and warns against common anti‑patterns and misconceptions to help teams adopt effective unit testing.
This article describes how a Chinese bank’s software development team leveraged AI techniques—text clustering and recurrent neural networks—to automatically classify and diagnose test-environment problems, dramatically reducing manual effort, improving issue visibility, and enabling self-healing mechanisms for faster, more reliable software delivery.
This article reviews JD.com’s automation testing framework, explores how Conway’s Law and organizational culture affect software quality, presents a coupon‑system redesign case, and offers practical guidance on metrics, team cohesion, and probabilistic effort estimation for high‑quality delivery.
This article examines the challenges of test data generation in fast‑moving software projects and presents a self‑developed Test Data Management solution that balances efficiency, usability, security, quality, generality, and cost through adaptive concurrency control, masking policies, and a multi‑master architecture.
This article explains how floating‑point numbers are represented in computers using IEEE‑754, illustrates conversion from decimal to binary, describes single‑ and double‑precision formats, outlines common precision, rounding, comparison, overflow, and associativity problems, and presents practical solutions such as high‑precision decimal types, integer scaling, and specialized libraries.
This guide explains how to balance implementation cost, maintenance cost, monetary cost, benefits, and risk when designing a test plan or strategy, outlines the differences between single test plans and test strategies, and provides detailed questions and considerations for test content, coverage, tools, processes, and utility to help teams produce practical, cost‑effective testing documentation.
The article reviews six common time‑related bugs—conversion, DST, precision, comparison, storage, and permission errors—explains their causes such as mismatched zones, outdated DST data, unit mismatches, overflow, and expired windows, and recommends development, testing, and operational safeguards like UTC normalization, unit definitions, proper data types, and monitoring.
This article explains mutation testing, its role in assessing test case quality, introduces the Java tool PITest, outlines a step‑by‑step workflow, presents mutation coverage results, and describes common mutation operators such as condition boundary, negated conditionals, and increments.
To address unreproducible problems in software testing, detailed documentation, repeated testing, environment replication, debugging tools, data monitoring, collaboration, and version control are essential strategies.
The recent Xiaohongshu app crash sparked public outcry and a viral screenshot blaming a developer, but the article explains that software bugs are inevitable, responsibility lies with the whole team, and proper debugging, testing, and process improvements are the rational response.
This article outlines how test engineers can proactively engage in each project phase—from requirement reviews and design assessments to scheduling, test case creation, code reviews, and risk mitigation—providing concrete tips for effective communication, early issue identification, and collaborative delivery of high-quality software.
The article examines common functional testing pain points—such as vague impact assessment, high regression cost, and poor test‑dev collaboration—and proposes a data‑driven solution that builds a code‑to‑test‑case mapping using dynamic call chains, static analysis, and coverage snapshots to enable precise test case recommendation and incremental coverage reporting.
The article explains how early test involvement and continuous testing activities—ranging from requirement analysis, risk assessment, and test planning to iteration‑level test execution, defect management, and post‑release verification—help improve software quality, reduce costs, and ensure successful project delivery.
The article explains how adopting a test‑left‑shift approach—integrating testing activities early in the development lifecycle through stages such as self‑testing, requirement and test‑case reviews, UI/product walkthroughs, showcases, and acceptance gates—can reduce rework, lower costs, and improve overall software quality and team collaboration.
The article outlines common reasons why others excel in functional testing—such as superior strategies, environments, tools, teamwork, experience, coverage, defect management, risk assessment, and continuous learning—and provides practical solutions to help you enhance your own testing capabilities.
Drawing on over a decade of testing experience at Alibaba, this essay examines how software quality shifts from a luxury to a strategic business asset, explores its varying importance across industries, and proposes ways testing teams can evolve into value‑driving functions within modern development organizations.
The article reinterprets James A. Whittaker's global exploratory testing by classifying testers into roles such as traveler, student, and official, and maps each role to specific roaming scenarios—shopping, landmark, overnight, dangerous, personalized, etc.—with concrete exploratory techniques and practical examples for software testing.
The article explains why testing is essential in software development and introduces ten widely used defect metrics—such as defect density, arrival rate, fix rate, effectiveness, severity, reopen rate, escape rate, average fix time, type distribution, and convergence trend—to help teams assess and improve product quality.
Amid China's push for digital transformation, ICBC's Software Development Center tackles testing inefficiencies by introducing a precision testing framework that leverages coverage analysis, call‑chain tracing, and AI‑driven test‑case recommendation to boost quality, reduce defects, and accelerate delivery.
This article explains the concepts of narrow and broad unit testing, the shift‑left and shift‑right testing strategies, compares Mike Cohn’s and Google’s test pyramids, discusses the limitations of unit testing, and shows how unit testing fits into traditional and agile development models.
This article introduces code‑level quality technologies, covering their background, architectural layers, code understanding methods, probe techniques, coverage metrics, smart unit testing, static analysis, and isolated‑function detection, and explains how these practices improve software robustness and defect‑recall efficiency.
This article introduces RunnerGo's automated testing features, detailing plan management, report management, scene import, task configuration, and how to view multi‑dimensional test results, while providing links to the project's GitHub and Gitee repositories for further exploration.
The article outlines a two‑layer architecture for code‑level quality techniques—CodeC for deep code understanding via static analyses and Codeπ for applications such as quality assessment, probes, health monitoring, and defect location—detailing methods like AST parsing, coverage metrics, intelligent unit testing, static analysis, and orphan‑function detection to enhance software robustness.
This article explains the complete lifecycle of software defects, clarifying the difference between bugs and defects, detailing essential and extended attributes, offering guidance on writing clear titles and descriptions, and outlining the step‑by‑step process from creation through verification and closure.
This article explains how to avoid common pitfalls in test case design by applying 5W2H requirement analysis, structuring cases with clear hierarchies, and using techniques such as equivalence partitioning, boundary value analysis, scenario flow analysis, and error guessing to create comprehensive, readable, and maintainable test suites.
This article recounts how a software test engineer leveraged ChatGPT to generate and refine test ideas for a mobile contacts export feature, highlighting the impact of query phrasing, timing, and AI response variability on test coverage and reliability.
This guide shows how to leverage ChatGPT together with tools like VS Code, Markmap, and PlantUML to automatically create complete, non‑redundant test case mind maps that cover boundary conditions, scenario coverage, and eliminate duplicate tests, boosting testing efficiency.
This article explains the distinction between code coverage and test coverage, outlines testing strategies across functional, code, and architectural layers, offers practical steps and visualisation techniques, and highlights how AI can enhance both kinds of coverage in modern software testing.
This article shares practical insights on business testing by outlining three essential stages—requirement review, test case design and review, and test execution—while offering tips on risk forecasting, bug reporting, and continuous improvement for software quality assurance.
This article outlines essential software testing points—including UI usability, functional correctness, performance load, security controls, and cross‑platform compatibility—explaining why enumerating each test item helps testers design comprehensive cases, detect defects early, and ensure reliable, secure, and user‑friendly applications.
Selecting an appropriate code coverage tool is crucial for ensuring software safety and reliability, and this article outlines ten key criteria—including compiler independence, ease of use, report clarity, support for safety-critical standards, integration flexibility, low overhead, language support, creative coding handling, security suitability, and licensing and support evaluation.
Static analysis is the examination of source code without execution, offering rapid, often real‑time feedback on code quality, and is widely supported by numerous open‑source and proprietary tools used within DevOps continuous delivery pipelines.
This article explains the concept of precise testing, illustrates industry implementations at iQIYI and ByteDance, examines current practices within China Industrial and Commercial Bank, and outlines future enhancements such as dynamic analysis and intelligent test case recommendation to improve test efficiency and risk assessment.
Writing code empowers software testers by automating test execution, reducing costs, expanding coverage, improving code quality, enhancing skill sets, increasing test case accuracy, shortening test cycles, boosting result reliability, streamlining test management, and accelerating data comparison, ultimately making testing more efficient and reliable.
The article explains why software testers should learn to write code, outlining twelve advantages of automated testing such as increased efficiency, higher quality, repeatability, better coverage, early defect detection, documentation, cross‑platform support, collaboration, real‑time feedback, stronger debugging, scalability, cost reduction, and competitive edge.
This article explains the concept of compatibility testing, outlines key characteristics, and provides a systematic approach for selecting test devices based on market positioning, delivery goals, technology constraints, test objectives, and resource considerations, while also covering resource pool building and execution methods.
The article explains why testers need clear system boundaries and authoritative test criteria, outlines methods to identify system components, and presents seven consistency dimensions—user requirements, comparable products, historical behavior, visual design, statements, standards, and purpose—to ensure reliable and repeatable testing outcomes.
This article shares practical habits and a structured five‑stage process for creating comprehensive test plans for an Order Management System, covering pre‑review preparation, design‑phase collaboration, post‑design verification, final review, and continuous improvement to ensure quality and alignment with business goals.
The article explains why test engineers need solid programming skills, highlights Java's cross‑platform advantages, rich libraries, and simple syntax, and provides a step‑by‑step guide covering core concepts, development setup, coding standards, practice exercises, common APIs, debugging tips, and essential testing tools.
This article provides a comprehensive overview of software testing, covering its purpose, various test types such as functional, performance, security, compatibility, reliability, user experience, internationalization, and automation, as well as career prospects and essential skills for testers.
This guide outlines twenty essential steps for creating an efficient software testing team, covering goal definition, strategy planning, hiring, process and tool setup, training, communication, continuous improvement, environment management, automation, agile practices, documentation, and fostering a culture of learning and collaboration.
This article outlines four practical QA scenarios—building a simple API automation framework, creating a Locust performance‑testing demo, writing functional test cases, and analyzing product requirements for hidden risks—while emphasizing how mastering ChatGPT can boost a tester's competitiveness.
The article examines how ChatGPT can generate test cases, automate scripts, and assist in various AI‑driven tasks while arguing that human testers remain indispensable for nuanced judgment, risk management, and continuous learning in the evolving software testing landscape.
This article outlines the purpose, responsibilities, and step‑by‑step workflow of the Test #1 position—an owner‑type quality architect in large‑scale projects—covering background analysis, scope planning, test case design, execution, risk management, full‑link rehearsals, and post‑release review, with practical tips drawn from JD’s real‑world experience.
This article provides software test engineers with 1‑3 years of experience a comprehensive roadmap to master fundamental testing skills, automation, performance, security testing, and essential programming languages, emphasizing systematic learning, practical application, and continuous improvement for career growth.
This article explains the challenges of testing in a rapidly evolving banking system and introduces a traffic recording and replay platform that automates test case generation, improves coverage, and reduces manual effort through web‑server, network‑stack, and application‑level recording techniques.
This article examines why evaluating software testers' performance is essential and outlines practical methods—including task completion, quality standards, communication, teamwork, learning ability, and contribution—to assess individuals, while also recommending environmental, training, and incentive measures to enhance overall test team effectiveness.
This article discusses common challenges in automated testing and provides strategies to address them, including gaining management approval, selecting appropriate tools, determining a starting strategy, and setting realistic expectations for automation.
This article shares practical insights and foundational principles for software testers, covering essential skills, the underlying logic of black‑box testing, input‑output modeling, and a concise 2W+1H analysis method to help both newcomers and seasoned professionals design effective test strategies.
This article explains what performance testing is, its goals, key metrics, common test types, and provides a step‑by‑step guide—including tool selection, requirement clarification, environment setup, script design, execution, and result analysis—using the RunnerGo platform for newcomers.
This article offers pragmatic, engineering‑focused advice on why unit testing matters, what makes a good test, when to write or skip tests, who should write them, and how to structure tests using the classic arrange‑act‑assert pattern.
A 2022 survey of Chinese software testing professionals uncovers how layoffs, new government policies, and emerging technologies are reshaping testing work forms, tool preferences, salary distributions, career entry routes, and the overall market landscape.
This article provides a comprehensive guide on handling insufficient testing time, improving test submission quality, and enhancing QA capabilities through systematic checklists, clear standards, risk management, and automation tools to ensure reliable software delivery.
This article outlines twelve essential software testing principles—ranging from user‑centric testing and lifecycle integration to risk‑based prioritization and third‑party verification—while also announcing the IDCF DevOps Hackathon, a 36‑hour event in Shanghai for building and launching a product.
This article compiles a comprehensive set of software testing interview questions covering test planning, test case design, bug identification, communication with developers, PO pattern usage, automation frameworks, API testing, performance testing, and related best‑practice answers to help candidates prepare effectively.
Test‑Driven Development (TDD) is an incremental, test‑first methodology that emphasizes writing failing tests before code, integrates refactoring, supports both unit and acceptance testing, addresses myths, tools, and its extension with Agile Model‑Driven Development, offering a disciplined approach to improve design and quality.
Google’s Bard, promoted as an AI search assistant to challenge Microsoft’s ChatGPT‑enhanced Bing, stumbled in a live demo by providing a false answer about the James Webb Telescope, prompting a market plunge and highlighting the critical need for thorough testing of AI‑driven search tools.
This article outlines a practical four‑step framework—defining standards, providing enablement, ensuring controllability, and fostering a collaborative atmosphere—to help testing teams support developers in conducting reliable self‑tests before production deployment.
The article explains the shift from unit testing to interface automation, outlines its advantages such as early testing and system robustness, details essential implementation techniques like protocol simulation, data‑driven testing, keyword‑driven execution, and provides practical steps for teams to begin API testing effectively.
This article outlines a complete software testing workflow—including requirement analysis, technical review, test design, developer self‑testing, test involvement, gray release, and full launch—highlighting key activities, stakeholder participation, and best practices for ensuring quality throughout the development lifecycle.
Effective test management should focus on three core areas—process standardization, rigorous requirement control, and continuous team development—by implementing clear workflow guidelines, thorough technical and test case reviews, proactive requirement reviews, and regular team growth activities such as monthly retrospectives and knowledge sharing.
This guide outlines the essential steps, templates, data-driven insights, and future planning tips for test leaders to create a comprehensive year‑end summary that highlights achievements, identifies gaps, and sets clear objectives for the next year.
This article outlines the most common software testing metrics, explains how they differ from broader software quality measures, and shows how teams at project, department, and executive levels can select and track the right indicators in both waterfall and agile environments.
This article examines the internal and external factors that influence exploratory testing, defines five testing levels from fully free to fully scripted, identifies suitable project types and domains, and offers practical ways to improve testers' exploratory skills and overall test effectiveness.
China Postal Savings Bank’s DevOps R&D Collaboration Platform and the Xingchen Platform’s Golden Bull Automated Testing System achieved top‑level evaluations in pipeline, CI/CD, and interface testing, showcasing how standardized tools and continuous delivery pipelines can dramatically improve quality, efficiency, and competitiveness in large enterprises.
CITIC Bank's Software Development Center successfully passed the China Academy of Information and Communications Technology's DevOps system and tool platform evaluation, achieving the highest "platform excellent" level across seven modules, and shared detailed insights on their testing service cloud and quality control platforms, the benefits of standardization, and future DevOps plans.
CITIC Bank's Software Development Center passed the prestigious "System and Tool Platform – Excellent" level of the DevOps Capability Maturity Model, detailing the evaluated Test Service Cloud and WuYueTian Quality Control platforms, the seven assessment modules, implementation challenges, and future DevOps plans.
This guide explains why test monitoring and control are essential for QA managers, outlines key metrics, data collection frequencies, evaluation methods, and best practices to keep testing projects on track and deliver quality software on schedule.
The article examines how testers often become scapegoats in software projects, detailing three layers of blame—from missed delivery schedules and unmet quality expectations to emergency releases—while arguing that underlying architectural and design flaws, not testing, are the true sources of product defects.
This article presents a comprehensive overview of intelligent test localization techniques—including spectrum‑based fault localization, error‑code driven build‑system localization, commercial revenue‑loss decision making, and UI case‑level tracing—detailing their motivations, methodologies, algorithms, and practical applications within automated testing pipelines.
This article explores Baidu's intelligent testing practices, covering spectrum‑based root‑cause localization, error‑code driven build‑system diagnostics, revenue‑change stop‑loss decision workflows, and search UI case‑level tracing, illustrating how data, algorithms, and engineering combine to reduce manual effort and accelerate issue resolution.
This article presents a detailed study on applying recommendation‑system techniques to test case prioritization for Bilibili's mobile apps, describing the problem definition, evaluation metrics, data processing, FM model selection, experimental results, practical deployment, and future research directions.
The article outlines a complete testing workflow for an activity lottery feature—from requirement evaluation, design, and case creation using equivalence and scenario‑based methods, through execution, gray‑release verification, and post‑release monitoring—emphasizing risk analysis, stability governance, rate‑limit safeguards, and financial loss prevention to ensure reliable, high‑quality releases.
This guide explains what performance testing is, why it’s essential, the key metrics such as throughput, response time, and bandwidth, outlines a step‑by‑step testing process, compares load, stress, endurance and capacity testing types, and reviews popular tools like JMeter, LoadRunner and NeoLoad.
This article outlines a practical five‑step guide for manual testers to evaluate the benefits of automation and smoothly transition to automated testing, covering case selection, tool evaluation, development management, execution‑reporting‑maintenance workflow, and effectiveness monitoring with key metrics.
Undetected bugs arise from vague requirement reviews, incomplete test coverage, lax test execution, limited environments, developer‑introduced defects, and insufficient exploratory testing, so teams should strengthen requirement analysis, design comprehensive cases, enforce strict test adherence, use gray releases, improve code reviews, automate coverage metrics, and adopt disciplined self‑testing and reporting to markedly reduce bug leakage.
This article describes Baidu's risk‑driven delivery approach, detailing the three current testing challenges, the design of a quality‑assessment system that uses machine‑learning (logistic regression) for risk identification, control and decision, and the resulting improvements in testing efficiency and quality.
This article analyzes Baidu's risk‑driven delivery approach, detailing how machine‑learning models identify, control, and decide on testing risks, replace manual judgments, improve test efficiency and quality, and deliver measurable savings and bug interceptions across large‑scale software projects.
Baidu’s risk‑driven delivery system applies a machine‑learning quality‑assessment model that automatically identifies, controls, and decides testing risks across over 50 features, enabling precise test selection, intercepting hundreds of bugs, cutting test waiting time from 50 to 2 hours, and paving the way toward fully automated intelligent testing.
This article examines how scriptless (no‑code) test automation is emerging as a cost‑effective trend that speeds software delivery, reduces maintenance effort, involves business analysts and technical experts, and highlights leading tools such as AcceIQ, Katalon Studio, Testim, Cloud QA, and Perfecto.
This guide walks a software test architect through gathering project information, applying a four‑step test‑strategy formulation method, defining product quality levels, analyzing risks, structuring overall, phase, and execution test strategies, and establishing a layered testing framework with concrete examples and visual diagrams.
This comprehensive guide explains what a test strategy is, how it differs from test policies, plans, and solutions, introduces a four‑step method for crafting strategies, and covers product quality goals, risk analysis, test layering, defect analysis, and practical techniques for effective software testing.
This comprehensive guide explains the role of a software test architect, outlines the six quality attributes of software products, details various test types and methods—including functional, reliability, performance, and usability testing—and presents a four‑step test design technique to create effective test cases.
The article explains Baidu's risk‑driven delivery approach for intelligent testing, outlines the current challenges of low‑risk projects, ineffective test tasks, and missed defects, and details how AI‑enhanced, fully automated testing, stable build pipelines, and precise risk‑assessment models enable unattended delivery and improve testing efficiency.
This article examines Baidu's risk‑driven, AI‑enhanced approach to unmanned software delivery, detailing the evolution of testing automation, the three human dependencies it eliminates, and the essential capabilities—comprehensive testing, stable builds, and precise risk evaluation—required to free testers from manual intervention.
This article presents an end‑to‑end intelligent testing framework that mines development‑stage risk dimensions, conducts admission risk assessment, extracts multi‑dimensional activity data such as coverage metrics, and applies model‑based risk evaluation to guide quality‑assurance decisions and improve release safety.
The article describes an intelligent test‑evaluation framework that gathers performance data, quantifies project, personnel, and code risk dimensions, feeds them into rule‑based and logistic‑regression models to produce risk scores and risk‑driven testing plans, and demonstrates how this approach identified thousands of high‑risk projects, prevented hundreds of bugs, and saved thousands of person‑days.
The article likens the strained developer‑tester relationship to a mother‑in‑law dynamic, explains why clear role boundaries and a well‑defined smoke‑testing stage are essential for quality handover, and offers practical steps for setting thresholds, selecting test cases, and balancing responsibilities.
Precise testing technology uses static code scanning and dynamic tracing to build a Neo4j call‑graph, automatically recommends test scopes and cases via diff analysis and weighted relationships—including call‑count, module, text similarity, and GCN—thereby improving test adequacy, cutting regression cycles, and dramatically reducing test execution time.
This guide explains how to decide which test scenarios to automate by evaluating cost, priority, feasibility, and business impact, while also outlining what should remain manual, essential prerequisites, tool selection, and a step‑by‑step approach to building an effective test automation strategy.
This article outlines eight fundamental principles—requirement‑based, scenario‑oriented, precise description, atomic, determinable, regression‑ready, independent, and orthogonal—that guide the creation of high‑quality test cases for developers, testers, and quality professionals across various testing scenarios.
This article explains how exploratory testing—a mindset that blends learning, design, and execution—can be applied to game QA, compares it with traditional and ad‑hoc testing, answers common questions, discusses its relationship with automation and AI, and shares practical tips from real‑world experience.
This article presents a systematic, six‑point approach for developers and testers to decompose UI‑related requirements—covering UI scope, data sources, data‑UI binding, user interaction handling, behavior tracking, and post‑release monitoring—to improve implementation clarity, collaboration, and delivery quality.
The article outlines how to design robust SpringBoot unit tests by first mastering business flows and external dependencies, preparing isolated test data, using Mockito’s @Mock/@MockBean and @Spy/@SpyBean correctly—including proper stubbing techniques—and applying best‑practice rules and the ACTS 2.0 framework for data‑driven, coverage‑verified testing.
Amid the current tech hiring slowdown, this guide outlines a comprehensive learning roadmap for software testers, covering fundamentals, Linux, shell scripting, web fundamentals, databases, packet‑capture tools, API testing, automation frameworks, mobile testing, TestOps, and performance and security testing to help engineers stay competitive and advance their careers.
The article explains how shift‑left testing, rooted in the waterfall model, moves testing activities earlier in the software development lifecycle to reduce defect‑fix costs, improve quality, and make developers the primary owners of product quality.
This article outlines the original test case review workflow, identifies its inefficiencies, and presents a comprehensive set of improvements—including pre‑review preparation, role assignments, meeting conduct, post‑meeting follow‑up, and presentation techniques—to help QA teams conduct more efficient and effective test case reviews.
