A seasoned test developer shares a decade‑long journey, detailing the evolution from functional testing to test automation, the construction of a comprehensive quality assurance system, practical tools for repetitive problems, and personal reflections on perseverance, collaboration, and continuous learning.
This article compares six widely used test case management platforms, explains their target audiences and key features, evaluates their strengths and weaknesses, and offers guidance on selecting the most suitable tool based on team size, workflow requirements, integration needs, and budget constraints.
The 2023 Software Quality Assurance industry survey, based on nearly a thousand valid responses, analyzes testers' employment status, satisfaction, background, technical skills, personal growth paths, team structures, AI/LLM usage, and future industry trends, providing data‑driven insights for professionals and managers alike.
The 2023 testing industry questionnaire, with roughly 850 respondents, reveals employment status, satisfaction scores, career change intentions, demographic distributions, salary trends, technical skill priorities, AI adoption rates, team structures, process bottlenecks, and forecasts for the coming year, offering a comprehensive view of the sector’s health and direction.
This article details Shentong's systematic approach to improving test completeness, covering test case design, a custom Quality Keeper workflow, code‑coverage measurement, precise regression strategies, automation effectiveness, issue‑driven optimization, and future plans such as front‑end coverage and AI‑assisted testing.
This article analyzes six typical time‑related bugs—including timezone conversion, daylight‑saving anomalies, precision mismatches, comparison errors, storage pitfalls, and permission expirations—and provides concrete design and testing safeguards for developers.
The article examines how API automation testing can be measured and implemented effectively, arguing that coverage and pass‑rate targets vary by team context, emphasizing cost‑benefit analysis, prioritizing core interfaces, and focusing on reducing feedback cycles rather than chasing statistical metrics.
This article explains the core concepts, rhythms, and practical applications of Test‑Driven Development (TDD) and Behavior‑Driven Development (BDD), illustrating how the red‑green‑refactor loop and business‑focused scenarios improve code quality, design, and collaboration between developers and stakeholders.
The article analyzes how quality assurance costs scale with product ambitions, compares small‑startup and large‑enterprise testing setups, and explains why automation and testing platforms require sustained investment that only pays off when aligned with business value and cost‑effectiveness.
The article examines why software testers often bear the blame in development projects, lists typical accusations they face, and offers concrete communication strategies and twelve practical recommendations to improve testing practices, clarify responsibilities, and foster better collaboration with developers and product owners.
The article examines why highly skilled test engineers are vulnerable during layoffs, highlighting the mismatch between technical prowess and business value, the importance of workplace networking, resource alignment, evolving testing roles, and current market trends such as platform decline, role consolidation, and growth in automotive testing.
The article traces the evolution of software testing roles in China from the early 2000s PC era through mobile-driven diversification, platform shifts, and recent AI and automotive trends, highlighting how responsibilities, tools, and career expectations have transformed over a ten‑year span.
This article explains how mid‑level and senior software test engineers are defined, highlights the career‑advancing value of certification, and presents a detailed testing skill map covering automation, performance, and security testing techniques and tools.
The article examines the ongoing debate about the necessity of dedicated QA roles, explains why high‑quality projects require systematic testing performed by professionals, outlines appropriate QA‑to‑development staffing ratios, discusses training and management of QA staff, and offers practical guidance for test case management and overall project quality assurance.
This article examines chart‑related requirements from a software tester’s perspective, outlining testing points, typical problems, and concrete case‑based test‑case designs for line, pie, and radar charts to improve test quality and efficiency.
This article provides a comprehensive guide on how test engineers, test leads, and test managers can structure their year‑end summaries by focusing on work responsibilities, project and business insights, and future planning, while offering role‑specific examples, tables, and practical tips to make the summary both meaningful and impressive.
This guide outlines essential principles for effective test automation within DevOps, covering investment planning, test case selection, result consistency, design techniques, language choice, application awareness, robustness, high‑quality test data, exploratory testing, and alert system implementation.
UnitGen, a dataset generation framework derived from UnitEval, combines unified prompts, quality pipelines, and extensible thresholds with language‑specific context strategies and ArchGuard checks to produce both documentation and test datasets for private AI code‑generation models, leveraging the open‑source Chapi AST engine.
This article explains what test cases are, their objectives, essential components, execution process, and the three core principles—accuracy, conciseness, and completeness—that guide the creation of high‑quality, maintainable test cases for reliable software testing.
This article presents a comprehensive test summary of a six‑month project involving eight applications, detailing test objectives, planning, execution cycles, case counts, defect statistics, quality metrics, and management lessons that together delivered a 99.9% transaction pass rate and valuable insights for test leaders.
This article explains how the open‑source AutoDev plugin builds an end‑to‑end AI‑assisted coding solution that fine‑tunes open LLMs, constructs a Unit Eval dataset, engineers prompts for unit‑test generation, and enforces quality through a unified write‑evaluate pipeline.
This article examines why many testing teams skip bug root‑cause analysis, outlines typical scenarios where such analysis is needed, and presents a practical four‑step method—including recording, cause marking, role attribution, and improvement planning—to enhance software quality and team efficiency.
This article explores the evolution of software testing, defines no-code automation testing, outlines its benefits, compares code‑based and no-code approaches, and presents a curated list of 34 leading no-code testing tools for 2023, while also explaining how QA teams can leverage these tools and integrate them with platforms like LambdaTest.
This article explores how software test engineers can leverage ChatGPT for tasks such as requirement analysis, test case creation, defect reporting, functional test generation, API test case generation, and automation script writing, thereby improving testing speed, accuracy, and overall quality.
The article explains why influence is essential for software testers aspiring to leadership, outlines key personal traits, presents common challenges, and provides a four‑step framework—including non‑violent communication techniques and practical case studies—to help testers effectively drive change and resolve conflicts.
This document outlines a complete test plan, testing strategies, resource allocation, schedule, risk management, acceptance criteria, and deployment procedures for an e‑commerce Double‑11 promotion, emphasizing functional, interface, and performance testing to ensure system stability and high‑quality user experience.
Quality assurance is fundamentally about exhaustive falsification to lower online risk, while the testing process seeks optimal ROI by balancing defect discovery against resource investment; a tester’s value hinges on business risk, system maturity, and the ability to become increasingly irreplaceable through deep domain knowledge, proactive risk mitigation, and innovative, end‑to‑end quality solutions.
The article examines three major Alibaba service disruptions, analyzes how insufficient testing and a lack of psychological safety among engineers may have contributed to the failures, and suggests ways to improve testing practices and workplace transparency.
The article defines testability as the precondition for conducting testing at each software lifecycle stage, explains its manifestations during requirements, design, development, and release phases, and illustrates the concept with a performance‑impact example from an e‑commerce order‑detail scenario.
This article explores how software test engineers can leverage ChatGPT to improve efficiency across the testing workflow, including requirement analysis, test case creation, defect reporting, functional and API test generation, and automation script development, while providing code examples and practical tips for integrating AI assistance into testing processes.
This document presents a detailed overview of a software testing project, covering client‑server testing differences, a full test plan and test case examples, an automated testing framework built with Python, as well as personal reflections on strengths, job motivations, and future professional development goals.
This article examines the emerging “shift down” software delivery approach, explains the limitations of traditional shift‑left and shift‑right testing, and shows how integrating both through platform engineering can improve efficiency, security, and agility in modern cloud‑native environments.
This article examines how ChatGPT can be combined with fuzz testing to automatically generate test cases, detailing the research process, design, implementation, performance metrics, discovered bugs, limitations, and future plans for improving AI‑driven automated testing in a real‑world e‑commerce environment.
This article examines how well‑structured test planning, balanced testing costs, risk‑aware quality practices, and project‑wide efficiency measures can significantly improve the return on investment of software testing activities.
This article explains what unit testing is, why it’s essential, and provides a step‑by‑step guide for writing Java unit tests with JUnit, integrating them into Maven projects, and generating detailed coverage reports using IDE features and JaCoCo.
TestAgent is an open-source 7B test-domain LLM that delivers multi-language test-case generation, automatic assert completion, and a rapid deployment framework, offering industry-leading pass@1 scores, a ChatBot UI, and detailed setup instructions for diverse hardware environments.
The article argues that the essence of software testing is risk avoidance, explores why bugs arise from user expectations, outlines three core challenges—investment, recursion, and measurability—and proposes balanced semi‑automated testing strategies to reduce bugs while acknowledging the limits of full automation.
A full‑stack test engineer should combine solid testing fundamentals with programming, web and backend development, database, OS/network knowledge, automation tools, DevOps practices, agile collaboration, and continuous learning to effectively design, execute, and improve comprehensive software tests.
This article introduces XMind2TestCase, a Python‑based tool that converts XMind mind‑maps into test‑case files (CSV, XML, JSON), explains its installation, command‑line and web usage, and discusses the advantages and challenges of using mind‑maps for test case design in agile environments.
This article explains how to prepare the Spark API environment, define prompts for an AI model, and automatically generate valid and invalid equivalence classes and corresponding test cases for a subway ticket self‑service purchase system, complete with expected outcomes.
This article outlines JD Tech's comprehensive quality‑assurance framework for user‑growth projects, covering responsibilities, challenges, core values, a diversified strategy, standardized processes, tool platformization, continuous operations, and measurable metrics to ensure high‑quality delivery across the product lifecycle.
The report analyzes SonarQube‑detected defects in Projects A and B, classifying them by type and severity, revealing that code smells dominate while null‑pointer bugs are unexpectedly frequent, and discusses why some defects are quickly fixed versus others remaining unresolved, emphasizing early detection, design rigor, and robust testing.
This article presents a comprehensive set of software engineering principles—including obsessive code detail, entropy control, test‑driven design, domain‑driven modeling, and disciplined coding habits—to improve code quality, maintainability, and team collaboration across development projects.
Relying solely on defect counts as a KPI fails to reflect a software test engineer’s true performance, so a multi‑dimensional evaluation—including test coverage, defect severity, automation, efficiency, problem‑solving, and teamwork—provides a more objective, comprehensive and fair assessment.
This article explains how systematic test case creation, clear verification steps, and disciplined bug tracking improve testing efficiency, ensure comprehensive coverage of core system logic and data flows, and help teams identify root causes to continuously raise software quality despite limited resources.
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.
