This article explains why evaluating test case effectiveness matters, defines effectiveness as the ratio of discovered bugs to total bugs, and introduces mutation testing with a fully automated robot that injects bugs, runs tests, compares results, and reports a quantitative effectiveness score.
The article explains what requirement analysis is, why it is essential for successful testing projects, outlines a step‑by‑step approach to performing it, and offers practical tips for improving analysts' skills, emphasizing business knowledge, user perspective, continuous learning, and proactive collaboration.
The article outlines seventeen essential and practical skills for software testers, ranging from rational clarity and staying updated on technology trends to effective planning, cross‑browser testing, front‑end communication, continuous learning, collaboration, and mastery of testing tools.
This article introduces JUnit 5, explains its architecture and key features, and provides step‑by‑step examples of writing, configuring, and running unit tests in Java, covering annotations, lifecycle methods, disabled tests, nested tests, repeated tests, assertions, timeout checks, exception handling, and parameterized testing.
This article outlines the nine critical competencies—ranging from analytical thinking and effective communication to automation, DevOps, and project management—that empower software testers to deliver high‑quality applications and thrive in modern development environments.
The article analyzes how unpredictable business volatility, digital transformation, and the convergence of Agile and DevOps will reshape software testing over the next ten years, emphasizing cross‑industry impact, automation growth, and the critical role of quality engineering.
This article provides a step‑by‑step tutorial on performing C++ code‑coverage testing using gcov, covering compilation flags, running the instrumented program, generating gcov reports, and creating detailed HTML reports with lcov, including command examples and configuration details.
This guide outlines seven practical steps—from mastering manual testing and programming skills to adopting the ATLC lifecycle, crafting automation strategies, and staying current with testing trends—to help anyone transition into a thriving career as a test automation engineer.
Interviews with 14 IT experts reveal that slow adoption, skill shortages, costly manual processes, and insufficient organizational support hinder automated testing, while opportunities exist through better tooling, containerization, and focused training to improve ROI and software quality.
This article provides a comprehensive overview of Test‑Driven Development, explaining its principles, workflow, relationship to acceptance testing and traditional testing, its impact on design and documentation, challenges in database development, integration with Agile Model‑Driven Development, common myths, adoption statistics, and a curated list of supporting tools.
This article analyses the historical background, recent trends, and future outlook of the software testing industry, identifies key factors influencing test engineers' career growth, and offers practical recommendations on technical skill development, management pathways, and navigating the changing QA landscape.
This article explains gcov, the GCC‑bundled C/C++ code coverage tool, covering its basic concepts, the workflow for generating coverage data, and the instrumentation technique using basic blocks and arcs to record execution counts.
This article introduces SonarQube, an open‑source platform for code quality management, explains its seven quality dimensions, provides step‑by‑step installation and configuration instructions (including JDK, MySQL, and scanner setup), demonstrates scanning a project, and summarizes its advantages for developers.
The article explains how testers can improve software quality by actively reviewing API definitions, understanding system architecture, evaluating database designs, reading code, and mastering configuration files, turning testing from a final checkpoint into a proactive, integral part of the development lifecycle.
This article presents a comprehensive 18‑point checklist covering smoke testing, installation/uninstallation, upgrade methods, business functionality, stability, performance, interface testing, usability, device compatibility, platform integration, special scenarios, permissions, security, data protection, phone features, competitor comparison, common oversights, and feedback channel establishment for mobile app testing engineers.
This guide enumerates the most important software, frameworks, commands, and knowledge areas—from mind‑mapping and bug‑tracking tools to HTTP protocols, performance testing, Android debugging, CI integration, IDEs, databases, servers, version control, and automation frameworks—required for a competent mobile app testing engineer.
This guide outlines a comprehensive learning path for aspiring APP test engineers, covering theoretical foundations, project management, testing processes, requirement analysis, test planning, case design, execution, reporting, metrics, defect management, and essential soft skills to bridge the gap between years of experience and actual capability.
To ensure stable and efficient single‑interface testing on our platform, we evaluated several mock frameworks—including RAP2, AnyProxy, Mock‑Server, and WireMock—and ultimately selected MockServer for its automatic protocol detection, simple configuration, extensive documentation, and built‑in fallback to real responses.
The article outlines a practical framework for evaluating hard‑skill competence in software testing by defining breadth (体, 面, 线, 点) and depth (表示层, 逻辑层, 数据层) of business‑logic knowledge, offering concrete examples and guidance for professionals to assess and improve their expertise.
This article details a practical approach to implementing automated testing in an information systems team, covering technology selection, framework setup, and real-world challenges encountered during the process.
This guide explains how to use the TFS Test Plan Management tool to import and export test cases, detailing step‑by‑step procedures, example screenshots, default file locations, and answers to common questions for testers seeking to manage their test case data efficiently.
This article details MaFengWo's travel‑booking team's end‑to‑end quality‑system construction, covering common QA misconceptions, project‑process control, comprehensive business testing, online issue closure, and tool development to achieve faster delivery, fewer bugs, and higher system stability.
The article explores how software testing is shifting from manual, delivery‑oriented practices to a real‑time, data‑driven quality model, detailing its historical evolution, architectural principles, case studies, and future directions within large‑scale internet enterprises.
This article explains how to transform product requirements into clear, executable test cases by defining unique conditions and deterministic results, discusses typical questions about coverage and edge cases, and provides concrete examples from game‑account and book‑purchase scenarios to illustrate effective case design.
This article outlines nine essential qualities and habits—such as curiosity, troubleshooting skill, perseverance, creativity, perfectionism, technical knowledge, confidence, persuasion, and programming background—that together form the roadmap for anyone aspiring to excel as a software test engineer.
This guide explains how to classify payment types, outlines functional, interface, and security testing methods, and lists comprehensive test points for payment amounts, processes, methods, and coupon handling to ensure reliable and secure payment flows in software products.
This article provides a detailed overview of payment testing, covering payment classification, common testing methods such as functional, interface, and security testing, key test points for payment flow, amounts, methods, and coupons, and includes illustrative diagrams to help testers ensure reliable and secure transaction processes.
The article explains the importance of bug analysis for improving product quality, outlines the information that can be analyzed, describes common bug resolution categories, discusses bug severity levels, and shows how various stakeholders can use bug metrics to drive process optimization and predict future issues.
Alibaba’s senior engineers share their curated list of essential technical books—from software testing and design patterns to AI, machine learning, reinforcement learning, Rust programming, and database architecture—explaining why each title is valuable for developers seeking deeper knowledge and practical insights.
The article explains how Azure DevOps teams separate application deployment from feature rollout using feature flags, enabling granular control, early user feedback, rapid rollback, and a staged release process without redeploying the application.
The article reviews three common boundary‑value bugs encountered during software testing, explains why they occur, shows the original C code that triggers each issue, and provides concise corrections to prevent off‑by‑one errors and buffer overflows.
The article examines two typical return‑code bugs encountered during software testing—one where a default success code is unintentionally returned in error scenarios and another where mismatched return‑code checks render error‑handling branches unreachable—offering concrete solutions and best‑practice recommendations.
This guide outlines a comprehensive software testing framework, covering basic smoke tests, functional, security, interface, compatibility, installation, performance, regression, and advanced testing practices, with detailed steps, responsibilities, and reporting requirements for development, testing, and product teams.
The article examines two typical return‑code bugs encountered during white‑box testing—one where error paths mistakenly return a success code and another where callers check the wrong value—explaining their causes and offering concrete remediation guidelines to improve error handling.
This article provides comprehensive guidelines for GUI testing, covering usability principles, conformity standards, help facility requirements, and rational layout rules to improve software interface design and user experience.
This guide outlines a complete software testing workflow covering basic smoke, functional, security, interface, compatibility, installation, performance, regression, and advanced testing stages, with detailed steps, responsibilities, and reporting requirements for developers, testers, and product teams.
This article debunks common myths about test automation, explains why scripts require ongoing maintenance, discusses why full automation is impossible, and offers practical guidance on balancing automated and manual testing using risk‑based, conversation‑driven, and exploratory approaches to maximize value.
This article explains common misconceptions about test automation, why it requires ongoing maintenance and human expertise, how to balance automated and manual testing, identifies key areas to automate using risk‑based, conversation‑driven, and exploratory approaches, and discusses how to evaluate the true value of automation.
This article expands on functional testing by exploring three key control areas—product knowledge, development quality through version control and test case integration, and environment configuration—offering practical insights and best practices for testers to enhance test effectiveness and drive project quality.
This comprehensive guide explains the most common software testing types—from Alpha and Beta to Security, Load, and Compatibility testing—detailing their purposes, execution contexts, and how they help ensure software quality before release.
The article examines the difficulties of developing and sustaining a multi‑million‑line C‑language database, highlighting complex flag‑driven logic, extensive testing pipelines, slow iteration cycles, and the need for automation, modularity, and robust engineering practices to ensure code quality at scale.
This article explains the concept of testing frameworks, discusses why reinventing wheels is discouraged, outlines the difficulties in selecting suitable frameworks, and provides a comprehensive list of general and mobile UI automation testing tools along with criteria for evaluating good frameworks.
The article analyzes how Google responded to a testing crisis by empowering a visionary leader, establishing supportive structures, encouraging innovation, and persisting over years to embed a quality‑centric culture that eventually led to decentralized testing, SRE adoption, and a shift toward test‑design engineers.
The article explains JD's high standards for software reliability, describes the testing team's shift toward test development, outlines core software testing concepts, standards, and the distinction between testing and quality assurance, while also promoting a free copy of the related book.
The article examines how the three pillars of technology organizations—organization, technology, and process—shape role divisions such as development, testing, and operations, explains the emergence of hybrid roles like test‑development, outlines essential skills for testing professionals, and reflects on career planning in the evolving tech landscape.
The article examines the background, challenges, and outcomes of research‑test integration at UC International, analyzes the evolution and current concerns of software testing careers, and offers insights on future testing roles, good‑enough practices, and recommendations for test engineers.
The second Hangzhou Testing Salon, organized by Youzan with partners KuJiaLe, Mogujie and 51 Credit Card, gathered over 300 attendees from 130 companies to share practical insights on full‑chain performance testing, a distributed pressure‑testing engine, rule‑based quality platforms, front‑end coverage tools, search‑service reliability and data‑quality monitoring.
This article outlines common challenges managers face with performance testing, explains when testing should be introduced, describes its process, types, metrics, and quality checks, and provides practical guidance for analyzing requirements and ensuring effective, repeatable performance test execution.
JD Security researchers attended the BRUCON conference to unveil a new fuzz‑testing operation that extends AFL with custom instrumentation, enabling faster testing across multiple CPU architectures and overcoming the limitations of existing fuzzers for closed‑source and non‑x86 systems.
The article details the structure, daily responsibilities, quality‑assurance processes, automation strategies, tool development, performance testing, and quality‑culture initiatives of the Shanghai testing team at Dada‑JD.com, illustrating how systematic testing and DevOps practices enhance product stability and development efficiency.
This article explains how to design comprehensive exception test cases by analyzing four dimensions—business requirements, operational requirements, standard requirements, and experience requirements—to ensure software robustness, reliability, and proper error handling before release.
The article explains the concept of closed‑loop thinking, illustrates how it can be applied to software testing through a concrete bug‑handling example, and shows how systematic feedback and reflection improve testing efficiency, knowledge reuse, and personal skill growth.
This article outlines thirteen common software testing antipatterns—from unstable or slow tests and manual test execution to treating test code as second‑class citizens and misusing TDD—explaining their negative impacts and offering practical guidance on building reliable, automated test suites.
This article reviews language‑agnostic software testing antipatterns, explains the test pyramid, defines unit and integration testing, lists frequent testing mistakes, and demonstrates why a balanced mix of unit and integration tests is essential for reliable, fast, and maintainable software development.
This article examines common software testing antipatterns, explains why testing the wrong functionality and over‑focusing on code coverage are misguided, introduces a mental model for prioritizing critical, core, and other code, and presents practical metrics and guidelines for effective, behavior‑driven testing.
The article discusses challenges of regression testing and proposes an incremental code‑coverage solution using a diff engine, AST analysis, and JaCoCo integration within a Jenkins CI pipeline, enabling precise test scope identification, visual coverage feedback, and improved collaboration between manual and automated testing.
This article expands on common software testing antipatterns, explaining why testing the wrong functionality, focusing on internal implementation, and obsessing over code‑coverage percentages can waste effort, and it introduces a mental model, practical metrics, and guidelines for writing effective, business‑oriented tests.
This article examines language‑agnostic software testing antipatterns, explains the differences between unit and integration testing, lists common testing mistakes, and demonstrates why a balanced test pyramid—combining both fast, maintainable unit tests and slower, broader integration tests—is essential for reliable software development.
This article explains how to begin API testing by clarifying its purpose, choosing critical interfaces, determining required system functions, and outlining a practical test design that covers environments, data, functional points, execution, and result verification.
The article explains how closed‑loop thinking—ensuring every task has a clear start, process, and feedback—can be applied to software testing to improve bug handling, foster continuous learning, and enhance overall testing efficiency.
This article examines the debate over who should write unit tests—developers or testers—by outlining the advantages and disadvantages of each role, explaining what unit testing is, how to design effective test cases, and offering practical guidance for implementing high‑quality automated tests.
The article outlines five typical mistakes new agile testers make—waiting for the next build, not fully integrating with the team, clinging to a quality‑control mindset, relying solely on manual testing, and ignoring the big picture—and offers practical advice for each to foster effective, collaborative testing within agile development.
This article reviews three typical boundary‑value bugs encountered during software testing—incorrect memory size checks, off‑by‑one retry counters, and misplaced increment operations—explaining their causes, showing original C code, and providing concise corrective solutions.
This article explains what Model‑Based Testing (MBT) is, why it outperforms traditional test design methods, outlines the step‑by‑step MBT workflow, showcases a logistics printing example, and introduces Suning’s MBT modeling tool with its key features and benefits.
This article presents pmock, a lightweight, zero‑learning‑cost mock framework for Java unit testing that integrates seamlessly with existing tests, explains the motivation behind unit testing, compares popular mock libraries, and details pmock’s configuration, usage, implementation, and known limitations.
Google’s test engineers (TEs) act as the glue between product, development, UX, and release teams, using automated testing, performance checks, and quality standards to ensure rapid, reliable product releases, while also tackling challenges such as battery usage tracking, data set evaluation, and accessibility consulting.
The article argues that testers should abandon a passive, isolated role and become proactive quality guardians who understand business, design logic, and user scenarios, using testing as a project‑management lubricant to drive continuous improvement and build a strong capability barrier.
This article outlines the comprehensive responsibilities of a software testing engineer, covering requirement review, documentation, system architecture awareness, process management, risk and time management, and provides practical guidelines to improve software quality and delivery speed.
This article outlines the essential knowledge for software test engineers, covering the defect lifecycle, status definitions, role responsibilities, defect management procedures, test case design standards, submission guidelines, priority and severity classifications, and practical tips for applying these concepts in real projects.
This article explains what a framework is, why automated testing is essential, its benefits and limitations, and outlines the essential components and common types of automation testing frameworks, providing practical guidance for building effective test solutions.
The article shares a test engineer's seven‑year journey, describing how their understanding of testing has evolved through four stages, outlining the broader responsibilities of test engineers, and offering practical advice on improving product quality, fostering collaboration, and ensuring technical solutions are effectively adopted.
This article explains what a framework is, outlines the purpose and advantages of automated testing, discusses its limitations, and describes the essential components and typical technology stacks of automation testing frameworks, providing practical insights for building effective test solutions.
This article explains why log testing is essential for server‑side applications, describes four log categories, provides concrete configuration examples, and lists eight practical checkpoints to ensure logs are useful, secure, and reliable during development and production.
This article offers nineteen practical pieces of advice—from empathizing with users and reading bugs to mastering automation and continuous learning—to help both novice and experienced software testers improve their skills and impact.
The article shares a test engineer’s seven‑year journey, highlighting four pivotal shifts in testing practice, redefining the engineer’s duties toward helping projects improve quality, quantifying quality metrics, and continuously refining tools and processes to enhance overall product reliability.
The article explains how early defect prevention through a strong test mindset, exploratory testing, and automated static code analysis with tools like SonarQube and Git hooks can dramatically reduce bug‑fix costs, improve software quality, and streamline development workflows.
By applying a PDCA‑based quality‑operation framework that aligns QA KPIs, drills defect data across dimensions, automates test‑gate checks, and drives continuous improvement actions, Meituan Dianping’s Intelligent Payment team reduced severe defect ratios, met defined metric targets, and boosted iteration efficiency while supporting rapid business growth.
The article outlines the comprehensive technical knowledge, testing fundamentals, business understanding, tool proficiency, coding ability, and communication skills required to be considered a senior test engineer, emphasizing industry experience, test process mastery, and continuous learning.
This article reviews a training session on bug reporting that introduces a four‑step approach—four Ws plus screenshot and clear preconditions/results—to help testers write precise, understandable bugs and improve collaboration between developers and QA teams.
The Qunar QTest Conference held on April 21 showcased a series of technical talks covering test environment governance, code coverage platforms, dynamic BadSQL scanning, machine‑learning‑based mobile performance testing, and case‑bug management systems, providing attendees with practical insights and future development roadmaps.
On World Book Day, nine Alibaba technology veterans share a curated list of essential technical books—covering software testing, design patterns, AI, machine learning, reinforcement learning, Rust, and database architecture—offering concise reasons why each title is valuable for developers and engineers.
This article explains how agile development—especially Scrum—and agile testing practices like continuous testing, TDD, automation, and continuous integration enable rapid iteration, higher product quality, and faster delivery in fast‑changing market environments.
The article shares a tester's three‑year journey, detailing real‑world problems such as session synchronization failures, configuration migration oversights, missing identifiers, and process compliance lapses, while offering analysis, root‑cause explanations, and practical lessons learned for improving software testing and operations.
This article explains how to create thorough test cases by outlining their purpose, covering functional aspects such as CRUD, GUI validation, data accuracy, business logic, backend checks, concurrency, and non‑functional concerns like browser compatibility, stress, API testing, and security, while emphasizing the need for project‑specific customization.
This article highlights frequently ignored testing problems such as browser navigation affecting data integrity, unnoticed JavaScript errors, boundary value issues in UI components, backend code review importance, improper handling of zero versus empty values, timestamp misuse, and inadequate validation of varchar and text fields, emphasizing meticulous testing for high‑quality software delivery.
This article explains how to set up gcov and lcov on Ubuntu, write a simple C++ program, compile it with coverage flags, generate .gcno and .gcda files, use lcov to create an HTML coverage report, and interpret the resulting line and function coverage percentages.
This article details how the AutoV IT framework addressed low test coverage, high maintenance costs, and data dependencies in a shopping‑cart checkout system, introducing embedded service startup, mock services, Excel‑driven test cases, and parallel execution to achieve up to 30% faster testing cycles and significantly higher confidence in releases.
The article explains why soft skills such as skeptical thinking, curiosity, analytical ability, and communication are crucial for software testers, complementing hard technical knowledge and enhancing defect detection, collaboration, and overall testing effectiveness.
The 2017 PractiTest software testing industry survey reveals worldwide respondent demographics, preferred testing skills, increasing multitasking and automation, widespread agile and CI/CD adoption, future technology priorities, and hiring expectations, offering a comprehensive snapshot of current practices and emerging trends for testers.
The article reports on the inaugural JD Quality Testing Technical Forum, where experts shared advances in performance testing platforms, test anti‑patterns, container‑based test environments, system‑graded testing strategies, and intelligent tools for handling massive data.
Test Fest is a company‑wide, short‑duration crowdsourced testing event that brings product managers, developers, designers, operations, and support staff together to explore a product, uncover bugs, improve compatibility, and generate actionable insights, dramatically boosting testing efficiency and ROI.
This article guides software testers who have only performed functional testing on how to transition to automation, performance, and security testing by learning programming, using Selenium with Java or Python, and leveraging online video tutorials to build a robust testing skill set.
This article outlines practical ways for beginners to self‑learn software testing, including recommended e‑books, video courses, participation in crowdsourced testing platforms, and gaining experience directly through work, while also offering tips for staying motivated and advancing in the field.
The article outlines sixteen key characteristics—including a skeptical attitude, uncompromising quality, user‑centric thinking, early testing, risk management, strong analysis, negative testing, effective negotiation, and teamwork—that together define what makes a software tester truly outstanding.
The article explains the differences between black‑box and white‑box testing, describing their definitions, advantages, disadvantages, common techniques, and why both approaches are essential for effective software quality assurance.
The article, translated from a StackOverflow discussion, examines whether a software project should have more testers than developers, presents multiple industry experiences, outlines factors influencing the optimal developer‑to‑tester ratio, and offers practical advice for improving testing effectiveness.
This article introduces automated testing, explains its purpose and benefits, outlines its pros and cons, identifies project types that are suitable or unsuitable for automation, and describes Baidu MTC’s mobile app testing services across three typical customer scenarios.
The article argues that even small internet firms cannot ignore operations as a capability, explaining how testing and ops improve functionality, stability, and business value, and outlining stages for integrating ops as a central control node within fast‑moving development cycles.
This article discusses quality assurance strategies for virtual businesses, covering layered testing approaches, external decoupling techniques, process simulation, risk prevention, and team building methods to ensure efficient and reliable platform operations.
The 2016 survey of roughly 2,000 Chinese software testing professionals reveals age, gender, education, experience, salary, job roles, testing types, skill gaps, and cloud and big‑data testing considerations, offering valuable insights into the current state and future outlook of the testing field.
