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.
This article explains how Zhongtong implemented a Java‑based code‑coverage service using Jacoco, integrated it into their CI pipeline, generated multi‑dimensional coverage reports, and refined testing workflows to improve software quality and reduce untested code.
This article examines why traditional testing must evolve for agile development, outlines the challenges of frequent builds, limited sprint time, performance and API testing, and provides practical guidance on planning, scope selection, parallel execution, DevOps integration, and choosing the right automation tools to boost collaboration and quality.
The article examines how software testing has expanded beyond bug detection in 2021, covering left‑shift/right‑shift testing, cloud‑based cross‑browser testing, AI‑driven tools, Selenium’s evolution, IoT performance testing, QAOps, blockchain testing, cloud automation, and the emerging NoOps model.
Transitioning from student to QA intern can be challenging, but by actively immersing in the workplace, communicating proactively, mastering business contexts, adhering to testing standards, and sharing knowledge, newcomers can quickly adapt, improve testing efficiency, and grow professionally within a fast‑paced development environment.
To thrive as a QA intern, quickly familiarize yourself with the workplace, communicate proactively with mentors, grasp business requirements through visual aids, follow testing standards, document and share knowledge, and continuously reflect on and improve your testing practices and automation skills.
This article reviews key insights from the book “How Google Tests Software”, highlighting Google’s view that quality stems from integrated development and testing, describing the distinct roles of SWE, SET, and TE, and comparing these practices with typical domestic software testing structures.
Google’s Test Certified program, launched in 2006 to promote testing culture through a five‑level certification system, registered over 1,700 projects, helped teams improve test coverage and reduce bugs, and was retired in 2016 in favor of the dynamic Project Health standard.
This article shares practical techniques to enhance software testability, covering strategies for bypassing graphical and SMS captchas, efficient test data creation, automated and brute‑force data injection, mocking services, and deploying test‑specific code without affecting production environments.
This article presents a detailed walkthrough of the FunTester testing framework architecture, covering its layered design, core modules for single‑ and multi‑project setups, multi‑protocol support, common request handling, business logic encapsulation, test flow, data construction techniques, and auxiliary tools such as moco API and JsonPath.
This article compares three Windows UI automation frameworks - Appium, Airtest, and Pywinauto - analyzing their principles, deployment environments, supported control properties, advantages, and disadvantages to help developers choose the right tool for their needs.
This article explains the various software defect terms, their classifications, how faults are detected through testing while defects require static analysis, and outlines current challenges and future directions for automated detection and repair of both faults and defects.
The article recounts a five‑day transition from student to test intern in Beijing, detailing the tools, platforms, testing processes, project workflow, and personal insights gained over two months of hands‑on QA work.
The article analyzes the key obstacles faced by software testing teams when working remotely—such as communication gaps, collaboration hurdles, technical failures, and documentation issues—and proposes practical solutions including video calls, automated regression testing, test‑driven development, and Selenium‑based tools.
This guide outlines a step‑by‑step roadmap for anyone wanting to master software testing, from analyzing job market demands and selecting relevant courses to leveraging search engines, videos, books, mentors, online communities, and workplace projects, while emphasizing disciplined time management and continuous practice.
This article explains why test cases are essential, outlines their purposes, presents key design principles and black‑box techniques, provides a web‑UI checklist example, describes basic test case components, and emphasizes the importance of thorough test case review.
This guide explains how to become a professional software tester by covering test case creation, essential testing methods, protocol basics, when to adopt automation, key testing tools, UI and API automation scripting, SQL proficiency, and Linux basics for effective testing workflows.
This article explains a "no‑data‑driven" approach to automated testing that minimizes in‑test data, moves data maintenance outside test cases, and demonstrates the method with a Java purchase‑API example, complete code, and practical tips for setup, teardown, and parameter management.
The article recounts Microsoft’s three‑decade journey in software testing, analyzing the shortcomings of the 1990s SDET/STE structure, describing two major transformations—merging test roles and adapting to cloud‑era speed—and explaining how organizational changes, quality‑ownership redefinition, and “left‑right” testing shifts enabled faster, more reliable releases.
This article outlines the most frequent obstacles teams encounter when adopting test automation—such as selecting appropriate methods and tools, managing massive test data, and timing automation phases—and provides practical strategies to address each challenge for more effective and reliable software quality assurance.
This article explains the concept of mock testing, its use in unit and API testing, illustrates real‑world analogies, compares popular mocking frameworks, and introduces several API‑mocking tools such as RAP, YApi, Moco, and DOClever for modern software development.
This article explains how to treat a polynomial addition and multiplication program as a black box, outlines its input/output format, describes a linked‑list implementation with key functions, and presents critical, equivalence‑class, and loop‑related test cases along with practical debugging tips.
This article shares the front‑search team’s experience on how test engineers can shift testing left by actively participating in requirement and design reviews, outlining consensus building, SDLC context, review procedures, current challenges, implementation steps, achieved outcomes, and future outlook.
The article outlines why code coverage is valuable for developers, warns against chasing high percentages without quality, emphasizes risk‑based assessment of uncovered code, and provides practical guidelines for incrementally improving coverage, integrating it into reviews, and setting sensible thresholds.
Test automation replaces manual testing by using tools to execute repeatable test cases, covering functional and non‑functional types such as smoke, integration, regression, security, performance, and acceptance testing, and discusses common frameworks like record‑and‑playback, modular, and library‑based approaches.
This article chronicles Microsoft’s testing journey from the 1990s separate SDET and STE roles, through the early‑2000s consolidation of those roles, to the modern cloud‑native “combined engineering” model that reshapes quality responsibility, accelerates delivery, and introduces specialized virtual teams for performance and security.
The article outlines best practices for writing test cases, emphasizing complete functional coverage, logical sequencing, and concise yet comprehensive descriptions, and details strategies such as equivalence class, boundary value, cause‑effect graph, error guessing, as well as capacity, stress, performance, security, and compatibility testing.
This article explains practical techniques—pairwise testing, clustering aggregation, greedy algorithms, and fuzzy‑logic‑based reduction—to dramatically cut the number of test cases while preserving coverage and improving testing efficiency.
This article traces Google’s testing organization from its early manual testing days through the Shift‑Left transformation, outlines the emergence of test engineering roles, and details the two main career tracks and hiring requirements for modern test engineers.
The article describes the challenges of maintaining test cases amid organizational changes and introduces a functional test case platform that centralizes case storage, supports version‑driven updates, enables reuse of business modules and base components, and outlines its backend MongoDB design, frontend mind‑map UI, and future roadmap.
Traditional testing suffers from low efficiency, unclear scope, and unquantifiable quality standards, especially in fast‑paced agile and microservice architectures; the article introduces a Precise Testing system that leverages bidirectional traceability, intelligent test case selection, incremental coverage analysis, and recommendation algorithms to make testing more accurate, automated, and data‑driven.
This guide outlines a comprehensive seven‑stage process—from planning and tool selection to environment setup, script design, execution, and result analysis—providing practical best‑practice notes to maximize test automation efficiency and coverage.
The article analyzes the mismatch between QA job market demands and candidate skills, outlines the traits and technical abilities that make testers highly sought after, and provides practical steps for testers to transition and advance their careers in a rapidly evolving software industry.
The article argues that the so‑called “shift‑left testing” is not a new concept but a rebranding of long‑standing testing principles, critiques its misinterpretation as moving test engineers left, and advocates for developers to own unit testing while professional testers focus on risk‑based, comprehensive quality assurance across the software lifecycle.
This guide explains why many IT budgets neglect quality assurance, presents data from the 2019‑2020 World Quality Report, and offers practical steps—ownership, prioritization, integration, automation, reporting, and documentation—to establish a robust QA workflow even with limited resources.
Exception testing, a distinct testing type from functional and performance testing, helps uncover system issues caused by system, dependency, or application anomalies, enabling designers to improve solutions and enhance overall system stability through comprehensive test case design and execution.
This article provides a comprehensive guide on creating a strong software testing résumé for social recruitment, covering essential sections such as personal introduction, education, professional skills, work experience, project experience, and education background, along with practical tips and common pitfalls to avoid.
This article explains why test automation is essential, outlines the three main types of automation tools, and provides a detailed framework for evaluating and selecting the most suitable tool based on project needs, team skills, budget, and integration requirements.
This article examines the growing need for comprehensive IoT testing, outlines how to select representative devices, and details the four main testing domains—security, performance, functionality, and compatibility—while offering practical guidance for QA teams to ensure high‑quality connected products.
The article explains how test engineers can extend their impact beyond functional testing by engaging stakeholders, adopting QAOps practices, listening to user feedback, exploring automation tools, participating in code reviews, focusing on user experience, meeting deadlines, and leveraging data science to improve software quality.
This article explains what automated testing is, outlines its key benefits such as simplified execution, reduced human effort, faster cycles and broader coverage, discusses when to adopt it, and provides a step‑by‑step guide for defining scope, selecting tools, planning, execution, and maintenance.
This article examines common pitfalls in code quality, testing, and development efficiency, analyzes their root causes, and proposes concrete, actionable solutions such as performance optimization, stricter coding standards, regular code reviews, improved testing practices, and enhanced team collaboration to boost overall software project success.
This article explains why fast, high‑quality delivery demands test automation, defines what a test automation framework is, outlines its various types and benefits, and provides concise comparisons of popular frameworks such as Robot Framework, WebdriverIO, Citrus, Cypress, Selenium, Cucumber, Gauge, Carina and FunTester.
A hidden bug occurs when a user's VIP subscription is repeatedly extended, causing the stored expiration timestamp to exceed MySQL's signed INT maximum of 2147483647 (January 19, 2038), which prevents the date from being saved correctly.
This guide explains why a well‑structured resume is crucial for software testing job seekers, outlines the five essential sections—personal intro, education, professional skills, work experience, and project experience—and provides detailed tips and common pitfalls to help candidates secure interview opportunities.
This article explains the concept of test coverage, describes various coverage techniques such as statement, branch, path, condition, and boundary-value coverage, outlines key metrics, provides a practical coverage matrix example, and offers actionable tips for improving overall software testing quality.
This guide explains the benefits of automated testing, outlines the main types of automation tools, and provides practical criteria—including platform support, ease of adoption, scripting flexibility, integration, analysis features, and licensing—to help teams select the most suitable solution for their CI/CD pipelines.
The article explains why traditional GUI testing is fragile, outlines the benefits of shifting to API testing—including early verification, automation, and comprehensive coverage of positive, negative and edge cases—and offers practical guidance for integrating API tests into an agile CI workflow.
Exploratory testing, introduced by Cem Kaner, is a flexible testing mindset that breaks conventional routines by designing, executing, and iteratively refining tests, and its integration with agile development enhances test strategy formulation, guides manual and automated testing, and improves overall software quality across various project complexities.
This article presents a curated list of eighteen challenging problems in software testing—ranging from measuring test sufficiency and effectiveness to test case reduction, layering, data preparation, automation, concurrency, rollback, compatibility, and formal verification—along with insights and potential research directions to guide practitioners and researchers.
This article explains how to validate a lottery API whose win probability changes with consecutive losses, outlines two practical testing approaches, and discusses the challenges of large‑scale, per‑user probability verification while preventing consecutive wins.
The article outlines five major reasons test automation initiatives stumble—over‑automation, neglecting manual testing, business‑logic changes, outdated test suites, and choosing the wrong tools—while offering practical guidance to keep automation projects on track and cost‑effective.
The article uses a whimsical conversation between a developer and a testing deity to explore why testing is essential, how it functions as sampling, the limits of defect detection, and practical strategies such as TDD, continuous integration, and requirement control to improve software quality.
API testing, a core form of backend functional testing, is essential because modern services share a single set of interfaces across web, mobile and mini‑programs, and mastering it provides the foundation for automation and performance testing while boosting employability.
This article introduces the Moonlight Box traffic‑recording and replay platform, explains its core functions and design principles, and presents multiple practical regression‑testing scenarios—including simple forward and reverse read replay, bidirectional replay, write replay, and compatibility adaptation—for both read‑only and write‑heavy interfaces.
This article explores how artificial intelligence is reshaping test automation by addressing maintenance bottlenecks, enhancing exploratory testing, and offering practical guidance for teams to adopt AI‑driven tools while remaining accountable for accuracy and results.
