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.
This article outlines the essential abilities every tester needs, explains why test design is the foundation of testing, and provides practical guidance on test case design methods, template structures, and best‑practice tips to improve test coverage and efficiency.
Effective unit testing—fast, readable, isolated, deterministic, and focused on a single behavior—relies on disciplined design, proper use of test doubles, the test‑pyramid hierarchy, meaningful assertions, continuous code‑review feedback, and mindful coverage, enabling safe refactoring, reduced maintenance cost, and higher confidence in software changes.
This article explains why performance testing is essential before large‑scale deployment and outlines fourteen critical software performance metrics—such as response time, request rate, error rate, CPU utilization, and concurrent users—to help development teams measure, analyze, and improve their products.
This article explains what unit testing is, why it matters, the characteristics of good tests, practical guidelines for writing effective tests in Flutter, test pyramid concepts, and how to integrate testing into design, refactoring, and team culture to achieve reliable, maintainable software.
This article examines how the automotive industry adopts continuous delivery, detailing the unique distributed, embedded, and safety‑critical constraints, the three‑stage deployment pipeline, test selection and load‑balancing strategies, and a case study of Tesla’s firmware rollout patterns.
The Vivo Internet Server Team describes how they integrated JaCoCo into their internal CI/CD platform to measure Java test coverage, explaining JaCoCo’s probe‑based instrumentation, the need for consistent compilation, handling incremental code and class‑ID changes, and showing that the resulting coverage data improves testing quality despite added effort.
This article examines the key difficulties of web test automation—such as coverage, dynamic element identification, synchronization, flaky pop‑ups, and reporting—and explains how AI‑driven and low‑code solutions, along with best‑practice techniques, can help teams achieve faster, more stable testing across browsers.
The article examines how the automotive industry adopts continuous delivery and DevOps techniques—detailing deployment pipelines, distributed embedded ECUs, safety‑critical testing, tooling, and real‑world observations from Tesla’s firmware release cycles—to illustrate the unique challenges and emerging solutions for rapid, reliable software updates in vehicles.
The article explains how Domain‑Driven Design combined with Onion Architecture creates a flexible, maintainable, and testable backend system by organizing code into concentric layers that isolate business logic from external concerns, supporting microservices, modular packaging, and appropriate testing strategies.
The author recounts three decades of experience in the software industry, describing early work as a technical writer at ACD, the hardware and tools of the era, waterfall SDLC, long‑cycle projects, support nightmares, cultural quirks, and a dramatic US Sprint incident that nearly sank the company.
This article traces the evolution of the software testing profession, shares the author’s personal career path from functional testing to test development, and provides a step‑by‑step guide—including architecture, code samples, and deployment—for creating a Python‑based API test data service and a Vue.js web UI to showcase it.
This article presents a comprehensive test development engineer competency framework comprising 34 ability models, each defined with a clear description, key points, and five progressive behavior levels that guide professionals from basic awareness to strategic mastery.
This article presents a comprehensive 34‑competency model for test development engineers, detailing ten core abilities—team leadership, strategic planning, plan execution, decision making, coaching, influence, organization coordination, cost awareness, customer orientation, and professionalism—each defined, highlighted with key points, and broken down into five progressive behavior levels.
This comprehensive handbook walks new test developers through understanding their role, mastering testing fundamentals, navigating various environments, and applying proven testing principles and workflows to ensure quality and stability throughout the software development lifecycle.
This comprehensive guide walks you through the fundamentals of software testing, covering test analysis and design, mobile testing techniques, performance and security testing methods, algorithm validation, data quality assurance, and effective cross‑domain project management for modern development teams.
This comprehensive guide explores the origins, evolution, and classification of software testing, outlines automation tools and conditions, discusses agile and DevOps integration, and provides practical step‑by‑step best practices for continuous testing using GitLab in early‑stage companies.
This article explains software testing fundamentals, classifies test methods, outlines general testing principles, dives into front‑end testing types and popular frameworks, provides code snippets for a minimal test runner, and compares TDD and BDD approaches, offering a comprehensive guide for developers.
This article explains what white‑box analysis is, why it matters for game feature testing, outlines a complete testing workflow from requirement to post‑release, and provides concrete examples and tips for QA engineers to improve test precision and efficiency.
This article explains why test cases are essential, outlines how to respond to common interview questions about their purpose, and provides a structured approach—what to test, how to test, and who should read the cases—to create effective, comprehensive test documentation.
This article explains what automated testing is, why it matters, compares manual and automated testing advantages and disadvantages, identifies modules that are suitable or unsuitable for automation, and provides concrete code examples for implementing and maintaining test scripts.
Effective communication—including active listening, non‑verbal cues, and stress‑management techniques—helps software test engineers avoid costly defects, foster teamwork, and navigate high‑pressure situations, ultimately boosting project success and career growth.
The article explains the concept of software testability, outlines controllability and observability factors, discusses cohesion and coupling, suggests practices such as TDD and design patterns, and introduces tools like testability‑explorer and Sonar for measuring and enhancing testability.
This article explains what test reports are, outlines their essential components and common types, discusses the challenges of handling large and fast‑moving test data in modern agile and DevOps environments, and describes how continuous testing and dashboards can improve software release decisions.
This article explains how junior testers and anyone seeking to expand test coverage can quickly and systematically write test cases using the GIVEN‑WHEN‑THEN template, and then apply an exploratory scenario association method to derive additional cases by modifying preconditions, steps, or expected results.
The article summarizes the 28th 58 Technology Salon held on April 27, 2022, featuring presentations on R&D efficiency measurement and mobile quality assurance, including detailed Q&A sessions that discuss metrics, data handling, performance testing tools, and practical improvements for development and testing teams.
The article outlines comprehensive quality assurance approaches for technical improvement projects, highlighting risk-driven processes, automated testing, business perspective integration, and the importance of addressing non‑functional requirements to ensure stable, reliable system upgrades.
This article explains the necessity and goals of unit testing, outlines common testing concerns such as independent paths, data structures, error handling, and boundary conditions, and provides a detailed guide to integrating and using OCMock in iOS, covering installation, mock types, stubbing, expectations, verification, and advanced techniques.
This article, the second part of a series on test fragility, explains the four components that can cause unstable automated tests, offers classification tips and diagnostic methods for each component, and provides visual illustrations to help engineers identify and remediate flaky test cases.
This article outlines a standardized test case review workflow, analyzes current challenges in agile environments, and presents a detailed design for an integrated online test case review platform, including framework, functional features, implementation steps, and best practices to improve test quality and risk management.
This article explains that unstable test cases stem from four main sources—test cases themselves, the testing framework, the system under test and its dependencies, and the underlying operating system and hardware—detailing typical causes and offering a classification guide for developers.
Unstable test cases, caused by shared resources and unchecked assumptions, can mislead developers, hide real bugs, and lead to unfair blame, so this article explains why preconditions must be verified, demonstrates flaky test examples, and offers practical strategies such as resource cleanup, unique test resources, and mock file systems to achieve reliable testing.
This article explains the scope, benefits, prerequisites, practical methods, differences from traditional testing, and future development of exploratory testing, offering guidance on when and how to apply it in agile, waterfall, and mixed‑mode software projects.
This article examines why some tests become flaky, showing that larger test binaries and higher RAM usage strongly correlate with instability, while the choice of testing tools has a smaller effect, and offers recommendations for reducing flaky tests in large‑scale continuous integration environments.
This article explains how the Finder system combines multi‑language code‑coverage collection, differential analysis, and call‑graph tracing to provide fine‑grained testing metrics, automate test‑case identification, and support continuous quality assurance across complex backend and frontend projects.
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 introduces the concept of QA in game development, explains its responsibilities from delivery testing to test delivery, highlights the importance of early requirement analysis, test case design, cost estimation, and collaboration with planners, and reflects on the value and confidence QA brings to the production pipeline.
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.
The article explains how the “knowledge curse” hampers testers from empathizing with real users, illustrates common registration‑flow pitfalls through screenshots, and proposes concrete steps—understanding users and bridging the testing‑user gap—to design more user‑centric test cases and improve software usability.
The 2021‑2022 TesterHome survey analyzes post‑pandemic changes in China's software testing industry, revealing salary distributions, regional and experience‑based differences, team sizes, role composition, automation impact, left‑right shift adoption, and emerging future directions such as AI, big data, AR/VR and autonomous driving.
This comprehensive report analyzes the 2021‑2022 software testing landscape, presenting questionnaire data from 1,859 respondents, salary distributions, regional and experience‑based trends, team sizes, entry pathways, test‑development ratios, automation impact, efficiency bottlenecks, and future directions such as AI, big data, and AR/VR.
This article traces the evolution of software testing, exposes three widespread misconceptions—including gender imbalance, the perceived lack of necessity, and low technical value—while presenting data, industry insights, and a concise skill checklist for modern test engineers.
This article reviews the historical evolution of software testing, explains the concepts of continuous testing within DevOps, outlines testing lifecycles, tools, and models, and looks ahead to emerging trends such as DevSecOps and AI‑driven autonomous testing.
The article shares five practical lessons from a senior engineer on how to manage upstream product interactions, run projects, coordinate testing, lead teams, and communicate with super‑iors, emphasizing early bug prevention, clear reporting, and empowering team members.
Dewu built a traffic recording and replay platform that captures fine‑grained, interface‑level Java traffic, stores it in Elasticsearch, and replays it via a Spring Boot‑controlled sandbox, enabling low‑cost, high‑fidelity regression testing, automated case classification, and early bug detection across multiple domains.
This article explains a modern layered architecture for UI automation testing, introducing a component layer that abstracts common UI elements, a page layer built on the classic page‑object pattern, a business‑logic layer for complex workflows, and a lightweight test‑case layer to improve maintainability and resilience to UI changes.
The article explains how to identify and remove redundant test cases by applying equivalence class partitioning and boundary value analysis, using a concrete account‑management example to reduce 28 generated cases down to 18 while preserving full coverage.
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.
This article explains what unit testing is, how to implement it with frameworks like Spock, provides a simple Groovy example, and discusses the advantages and drawbacks of unit tests for software development.
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 article outlines a comprehensive set of software quality, test process, and delivery metrics—including coverage, execution, defect rates, and release success—explaining their purpose, calculation formulas, data sources, and example results to help teams assess and improve product quality.
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 article outlines a comprehensive test‑analysis framework, detailing six essential questions, a four‑step methodology (modeling, basic test‑case design, data supplementation, and expansion), product and project overviews, quality‑attribute mapping, business‑process modeling, risk assessment, and functional test‑case design techniques.
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.
