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.
This document outlines a comprehensive software testing plan covering project overview, test preparation, detailed strategies for unit, interface, functional, UI, UAT, and performance testing, along with scheduling, common standards, and checklist guidelines to ensure quality and risk mitigation.
This article outlines a comprehensive competency framework for test engineers, detailing five proficiency levels—basic understanding, proficient, flexible application, comprehensive application, and innovative mastery—across 28 key testing activities such as analysis, design, planning, execution, automation, security, and DevOps, providing clear behavioral descriptions for each level.
This article explains the distinct concepts of code coverage and test coverage, outlines their respective measurement methods, compares their advantages and disadvantages, and provides guidance on selecting appropriate tools and practices for effective software quality assurance.
This article explains how systematic unit testing boosts R&D efficiency, outlines its origins, methods, tools, and evaluation standards, and shares practical insights from JD Retail specialists on implementing effective unit tests in real‑world projects.
This article explains why test cases are essential, outlines the complete workflow from requirement analysis to case maintenance, and provides practical tips and tool recommendations—including Excel and Xmind—to help testers design, review, and manage high‑quality test cases efficiently.
The article analyzes common reasons why defects escape testing and appear in production—ranging from missed test cases and environment differences to incomplete releases—and offers a step‑by‑step checklist of practices to improve testing, release processes, and risk mitigation.
YouZan’s traffic‑replay platform records real production calls and replays them in test environments—both read‑only and mock‑write modes—to automatically verify thousands of marketing interfaces, visualize scenario coverage, capture low‑traffic cases, and has already enabled zero post‑launch failures while guiding future expansion into deeper coverage and performance testing.
This article compiles a comprehensive set of software testing interview questions typically asked across three interview rounds, covering self‑introduction, wake‑up feature design, performance testing, project delivery, automation, leadership, and career motivations to help candidates prepare effectively.
This article explains five typical pitfalls that make unit tests ineffective—testing per function instead of behavior, chasing code‑coverage, over‑reliance on mocks, writing tests that never fail, and allowing nondeterminism—while offering practical guidance on how to avoid each issue.
The Indian tax e‑filing portal built by Infosys collapsed shortly after launch due to inadequate testing, poor project management, and repeated technical glitches, highlighting critical lessons for large‑scale IT operations and delivery.
The MTSC2021 Shenzhen conference, a premier software testing summit organized by TesterHome, will be held on November 19‑20, 2021 at the Dongxi Road International Hotel in Shenzhen, offering registration information, audience guidance, participant benefits, and a comprehensive list of confirmed and candidate technical topics covering testing, DevOps, AI, cloud, and game development.
This article curates a selection of Chinese-language resources on test development, including internship experiences, growth discussions, business and requirement analysis guides, knowledge‑expansion materials, and a 2021 first‑half article collection, aimed at helping aspiring test engineers find structured learning paths.
This article presents a curated set of 140 software testing interview questions covering topics such as API testing, automation frameworks, performance testing, CI/CD, database operations, Selenium, mobile testing, and related concepts, offering valuable preparation material for candidates.
This guide explains how to define automation goals, choose suitable test types, select appropriate frameworks and tools, and apply best practices for creating, running, and maintaining test scripts to improve ROI and product quality.
This article shares practical experiences and advice on learning software development by copying code, covering where to find source code, official documentation, exemplary implementations, and search engines, and illustrates the approach with real‑world examples from the FunTester testing framework.
The article shares a tester’s two‑year growth experience, illustrating how testing focus shifts from basic functional checks to comprehensive test plans that combine interface, data‑construction, mock, and debugging techniques for various backend, frontend, and full‑stack scenarios.
The article examines why many automation testing initiatives fail to deliver value, introduces a set of practical metrics such as test case count, execution frequency, success rate, coverage, EMTE, ROI, and bug‑detection efficiency, and explains how to combine them to assess and improve automation effectiveness within software development processes.
This article explains the importance of test automation frameworks, outlines various framework types such as tool‑centric, project‑specific, and keyword‑driven, details essential components like test libraries and CI integration, and provides practical guidance for building and maintaining effective automation solutions.
The article outlines Google’s best‑practice guidelines for code coverage, emphasizing its workflow benefits, the cultural impact of increasing coverage, the limits of high percentages, the importance of uncovering uncovered code, and practical steps for progressively improving coverage across projects.
The article explains precise testing—a data‑driven approach that maps test cases to source code changes to improve test efficiency, coverage measurement, and impact analysis—while discussing its architecture, implementation methods, benefits, and the practical challenges of adopting it in agile projects.
This article compiles the Q&A from iTech Talk 17, where experts from iQIYI, Meituan, Tencent, and ZhaiZhai share practical solutions for precise automated testing, intelligent test instrumentation, APP diff automation, and visual AI evaluation, revealing real‑world challenges, implementation details, and measurable benefits across large‑scale production environments.
This article explains what code coverage is, why it matters, the different coverage metrics, how coverage measurement works, and reviews several mainstream tools across various programming languages.
This article explains agile testing, contrasts it with traditional testing, and details ten guiding principles—including continuous feedback, customer value, face‑to‑face communication, courage, simplicity, continuous improvement, adaptability, self‑organization, people focus, and enjoyment—that help testers and agile teams deliver high‑quality software efficiently.
Integration testing, also known as assembly or joint testing, verifies that combined modules function correctly as a subsystem, covering objectives, processes, test planning, case design, execution, and reporting, while addressing challenges of cross‑team collaboration and ensuring overall system reliability.
This article explains how traditional, lengthy test‑strategy documents can be replaced by a concise, one‑page visual diagram that clearly presents what to test, how to test, guiding principles, and the roles of test left‑shift, test quadrants, test layers, and test right‑shift, using a real‑world example to illustrate the approach.
At the 2021 China Internet Test Development Conference, ZTO Technology’s senior architect Gong Linhua detailed how their thousand‑person team builds a robust quality assurance system through business testing, continuous innovation, specialized training, and precise metric‑driven management, aiming to accelerate delivery while maintaining high software quality.
This article explains how to determine the right amount of testing for a software product by providing evaluation criteria, a step‑by‑step testing strategy—including recording processes, unit, integration and end‑to‑end tests—coverage types, tools, and how to incorporate field feedback for continuous improvement.
The article explains the distinction between a test specification (technical‑focused test scheme) and a test plan (project‑focused schedule), describes when each should be created during a project lifecycle, and provides templates, methods, and reporting formats for effective software testing.
This article identifies the most common obstacles teams face when adopting test automation—such as choosing approaches, selecting tools, managing data, and timing tests—and offers actionable solutions to help organizations implement effective, sustainable automation pipelines.
The article reviews four in‑depth talks from MTSC2021 Shanghai, detailing how ZTO, Meituan, ByteDance and Kujiale build large‑scale testing frameworks, event‑tracking QA, advertising system reliability, and multi‑dimensional online inspection to ensure product quality across complex business scenarios.
This article explains how test engineers can embed quality into software projects by contributing at the requirement, implementation, and organizational levels, turning testing into a strategic asset that enhances team collaboration, reduces rework, and drives continuous improvement.
This article outlines the essential concepts, four‑step workflow, and practical tips for beginners to define scope, choose tools, design frameworks, execute test cases, and generate effective automated testing reports.
This article argues that traditional, step‑by‑step test cases are becoming obsolete, advocating for alternative test design methods such as mind maps, matrices, user‑story acceptance criteria, and emphasizing exploratory testing, codeless automation, and knowledge‑centric approaches to improve efficiency and maintainability.
This article describes a solution that merges incremental unit test coverage into overall test environment coverage by leveraging Maven Surefire Report Plugin and JaCoCo, detailing steps from CI platform integration, plugin configuration, report generation, to coverage platform processing, enabling comprehensive coverage analysis for release admission.
This article outlines a comprehensive seven‑stage test automation strategy, covering planning, method selection, tool choice, environment setup, script design, execution, and result analysis, while offering practical tips for each phase to boost efficiency and reliability.
The article explains how defect repair costs increase the later they are discovered, argues for shifting testing activities left into the requirement phase, describes three requirement granularities (Epic, Feature, Story) and outlines specific quality activities for each level to achieve early defect detection and lower overall development cost.
The article surveys five major software testing organization models—centralized, decentralized, hybrid, third‑party, and “no‑testing”—explaining their evolution, characteristics, advantages, and challenges, and discusses how agile practices and business needs drive the shift toward integrated or outsourced testing structures.
Effective test automation relies on well‑designed frameworks, and this article explains why automation is essential, categorizes tool‑centric, project‑oriented, and keyword‑driven frameworks, details core components such as test libraries, data management, reporting, CI integration, and outlines a step‑by‑step implementation process.
This article explains how a lightweight test‑automation platform built with SpringBoot, MyBatis and Layui dramatically reduces data‑generation and validation effort, streamlines integration testing, and boosts overall testing productivity for developers and QA engineers.
The guide explains YouZan’s low‑code BOS platform, its component‑based architecture, and a multi‑level testing methodology—including automated component, product, and workflow tests, traffic replay, performance checks, and a robust fallback mechanism—to ensure seamless migration and reliable operation of digitized business processes.
This article presents a comprehensive, automated solution for API robustness testing that extracts baseline cases, generates exhaustive parameter‑level test data, executes them at scale, and analyzes results to identify abnormal responses without manual effort, thereby improving testing efficiency and software quality.
Overusing mocks in unit tests can make test code harder to understand, harder to maintain, and give a false sense of correctness, so developers should recognize signs of excessive mocking and consider alternatives such as hermetic servers or fake objects.
This article connects classic Chinese idioms to software testing concepts, explaining test purpose, policies, strategies, tool usage, risk management, and improvement practices through vivid examples and practical guidance for building more reliable testing processes.
This article explains the fundamental concept of code coverage, its basic classifications, the various metrics such as function, line, branch, and condition coverage, factors that affect coverage, its significance for software quality, and practical ways to measure and improve it.
The article analyzes Google’s definition of Test Engineers, compares it with domestic testing roles, discusses why test plans fade, and introduces the ACC (Attribute‑Component‑Capability) method as a practical alternative for quality assurance in modern software development.
