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.
The article explores how software testing teams can identify and implement both technical and process-oriented innovations—ranging from tool usability improvements and automation to standardization, templating, and cross‑domain borrowing—to enhance efficiency, quality, and overall value.
This article explains how Qunar's Qunit testing framework was enhanced with automatic baseline generation and new tags—dataMode, dataHolder, dataAssert, and dbAssert—to simplify test case creation, maintenance, and verification while reducing reliance on external data services.
The article examines the growing crisis in the software testing industry, highlighting external stagnation, internal role changes at Huawei, the impact of DevOps and cloud technologies, and proposes how testers can adapt by expanding skills, embracing automation, and positioning themselves as quality guardians.
This article explains the fundamentals of unit testing, compares it with integration testing and TDD, describes characteristics of good unit tests, shows a practical .NET example using XUnit, FluentAssertions and Moq, and offers architectural tips for writing test‑friendly code.
With increasing emphasis on user experience, this article introduces five widely used web performance testing tools—HP LoadRunner, Apache JMeter, Load UI, Httperf, and Siege—detailing their capabilities for load simulation, functional testing, and performance analysis to help developers and testers optimize application reliability and speed.
This article examines the common pain points of integration testing in distributed systems, including weak cross‑coupling coverage, lack of clear standards, chaotic composite scenarios, and insufficient risk assessment, and discusses current mitigation approaches and open questions for future exploration.
This article outlines common compatibility testing challenges across software components, online upgrades, driver interactions, and operating system variations, and provides practical testing strategies to detect and mitigate issues such as version mismatches, file ordering, and security software conflicts.
This article presents a collection of fifteen C programming quiz questions, each accompanied by the original code, multiple‑choice options, the correct answer, and in‑depth explanations covering topics such as setjmp/longjmp, pointer casting, recursion, sizeof, function pointers, variadic functions, and static variables.
The 2005 Mizuho Securities “fat‑finger” incident, caused by a trader’s input error and a hidden bug in the Tokyo Stock Exchange’s Fujitsu‑built trading system, led to a ¥400 billion loss, sparking extensive litigation that highlighted responsibilities for software bugs, system testing, and operational risk management.
A 2005 fat‑finger error by a Mizuho trader triggered a ¥400 billion loss, leading to a landmark court case that clarified liability for software bugs in financial systems and highlighted the need for rigorous testing and evidence preservation.
This article introduces the concept of basic quality within a product competitiveness model, outlines key evaluation dimensions such as functionality, performance, compatibility, and security, and provides step-by-step guidance on defining metrics, selecting testing methods, and quantifying results, especially for mobile applications.
This guide explains why vague "error" messages frustrate developers, outlines the essential role of non‑technical staff in quality assurance, and provides a step‑by‑step template for creating clear, actionable bug reports that help engineers resolve issues faster.
This article provides a comprehensive checklist for code reviewers, covering formatting, design, readability, functionality, security, testing, performance, and resource usage, while explaining why many of these aspects can be automated and how to balance manual inspection with tooling.
The article explains how Docker’s lightweight container technology speeds up test environment setup, reduces resource consumption, supports blue/green deployments, and simplifies production orchestration, making it an essential tool for modern development teams seeking efficient, reliable software delivery.
The article examines Quora's engineering practices—including static analysis, post‑commit code review, automated testing, and systematic legacy code cleanup—that enable the company to maintain high code quality while sustaining fast development cycles.
