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.
This article explains Test‑Driven Development (TDD) by outlining its advantages, underlying principles, step‑by‑step workflow, core guidelines, testing techniques, and practical tips, helping developers adopt the practice efficiently with minimal cost.
This article surveys the latest software testing trends—from security, AI‑driven testing, static analysis, and precise testing to cloud, IoT, open‑source tools, container‑based DevOps, agile, big‑data, and mobile testing—highlighting opportunities, challenges, and future directions for test engineers.
This article outlines a tester’s personal journey through four stages—learning and verification, confronting misconceptions of conflict with developers, proactive collaboration, and finally embracing responsibility—highlighting how testing evolves from a simple validation task to a strategic, risk‑reduction discipline.
Based on a survey of roughly 2,000 Chinese software testing professionals, this report analyses company characteristics, testing‑development ratios, career advancement, training frequency, testing tools, and process metrics, offering insights into current industry trends and recommendations for QA practitioners.
This article explores how project management’s cost‑schedule‑quality triangle, ISO quality definitions, the software quality “iron triangle” of process, organization, and technology, and the six quality characteristics guide developers and testers in improving product quality through systematic thinking and practical testing methods.
This article outlines sixteen key characteristics and habits—such as maintaining skepticism, prioritizing quality, focusing on user satisfaction, thinking from the user's perspective, prioritizing tests, avoiding over‑promising coverage, embracing feedback, starting early, managing risk, conducting market research, honing analytical skills, considering negative scenarios, making sound judgments, negotiating effectively, avoiding blame, and observing diligently—to help testers excel in their roles.
This guide explains why precise bug localization is crucial for testers, outlines systematic approaches with real-world examples, and offers practical tips—including preserving the crime scene, asking the right questions, and interpreting HTTP status codes—to efficiently identify and resolve issues across web applications.
This article introduces the basic concepts of software testing, covering defect management tools, bug reproduction prerequisites, JIRA issue types, classification methods, severity and priority levels, status lifecycle, and the complete bug handling workflow.
This article provides a detailed overview of software testing fundamentals, covering testing stages across project lifecycles, classifications such as black‑box, white‑box, and gray‑box testing, functional and performance testing, manual versus automated testing, and specialized tests like smoke, regression, random, exploratory, and security testing.
The author shares a detailed personal journey from a novice software tester to a testing leader, describing how self‑learning automation tools like Selenium, Appium, and RobotFramework, adopting performance testing, establishing quality processes, and leading a team transformed both personal growth and product quality.
The article examines the large disparity between academic research and engineering application of software testing technologies, highlights mature and emerging methods, and offers practical guidance for testers to build a systematic view, stay informed, and translate research breakthroughs into effective engineering solutions.
The article translates James Bach's "Seven Kinds of Testers", describing seven tester personas—Administrative, Technical, Analytical, Social, Empathic, User Expert, and Developer—along with practical advice for each role and commentary on their impact in software testing.
The article outlines how test strategy, risk‑based testing, automation, TDD, defect‑location tools, CI/CD and agile practices can collectively boost development efficiency, reduce waste, and enhance product quality throughout the software delivery lifecycle.
This article, featuring Baidu QA expert Yang Xiaohui, examines the motivations, benefits, common pitfalls, and strategic considerations for implementing test automation, emphasizing clear goals, stakeholder collaboration, scope definition, timing, and the broader impact on software quality and development efficiency.
This article outlines how teams can transition to agile development by adopting Scrum or Kanban, emphasizing self‑organization, realistic planning, continuous integration, automated testing, regular retrospectives, and servant‑leadership to sustainably deliver business value while managing technical debt.
The article uses a bus‑schedule analogy to illustrate how long release intervals and frequent hotfixes frustrate customers, then proposes shorter release cycles through better iteration planning, demand splitting, stronger development capability, and robust testing to achieve continuous, rapid delivery.
The article critiques common automation‑testing practices—outsourcing massive script teams, low defect detection rates, and over‑reliance on AI‑driven tools—arguing that true efficiency comes from better script quality, tighter management, and empowering engineers to write and maintain their own Ruby‑based ActionWord scripts rather than chasing superficial smart‑generation solutions.
The article outlines five common self‑imposed pitfalls—blind arrogance, reliance on others, obsessive tech focus, nitpicking, and lack of clear goals—that hinder test developers' growth, and offers practical advice for overcoming them to succeed in the evolving testing industry.
This article explores how software testers can leverage big data and data‑mining techniques, particularly a Naive Bayes classifier, to objectively prioritize defect fixes, improve testing processes, and address uncertainties inherent in traditional testing workflows.
This article explains what exploratory testing is, traces its growing importance in modern rapid‑iteration product development, and presents practical techniques—including free‑form deep testing, scenario‑based traversal, strategy‑driven extrapolation, and feedback‑driven iteration—illustrated with real‑world mobile app examples.
