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.
This collection provides a curated set of links to articles covering performance testing strategies, notable bug analyses, and practical web crawling implementations, offering valuable insights for software testers and engineers seeking to improve testing practices and data extraction techniques.
Effective test automation hinges on solid test design, and this article outlines five practical guidelines—keeping tests concise, reusing components, ensuring independence, defining clear purposes, and prioritizing real users—to boost test reliability and maintainability.
This guide walks you through the complete software testing lifecycle—covering requirement collection, test strategy, test planning, execution, pre‑release checks, and final release best practices—to ensure high‑quality, reliable software delivery.
This article outlines the essential knowledge, tools, and practical steps a beginner or career‑switcher needs to acquire—including testing fundamentals, functional testing, databases, Linux, networking, version control, programming basics, automation, and performance testing—to successfully land and perform in a junior software testing role.
Software testing is increasingly rapid and automated, yet testers often fall prey to cognitive biases—such as similarity, consistency, confirmation, conformity, inattention, and negativity—that cause missed defects; understanding and countering these biases can markedly improve test coverage and product quality.
The article explains that stable tests should verify only the parameters that affect the behavior under test, use matchers to ignore irrelevant data, and apply contract testing or realistic fakes for microservice calls instead of over‑relying on mocks, thereby improving readability and resilience.
This article presents practical strategies for reducing software testing expenses—including early testing, balanced documentation, risk‑based testing, leveraging production data, prioritizing API over UI automation, adopting open‑source tools, optimizing infrastructure, training, process improvements, and selective outsourcing—while maintaining overall product quality.
This article outlines a comprehensive roadmap for establishing a test automation framework, highlights key aspects such as exploratory testing, user experience, accessibility, dynamic content, and offers best practices for test case design, handling slow or failing tests, and maintaining reliable automated suites.
This guide explains why companies outsource software testing, outlines key factors such as outsourcing models, geographic location, service agreements, flexibility, and quality improvement, and provides a step‑by‑step process for investigating, interacting with, and selecting the right testing service provider.
This article explains how to develop a comprehensive UI testing plan, covering prerequisites, essential components, test strategies, and detailed test case creation to ensure effective UI/UX validation across browsers and devices in modern applications.
The demand for skilled test automation engineers continues to rise, as companies still rely on manual and exploratory testing while increasingly automating regression, performance, and load tests, making continuous learning essential for a rewarding career in software testing.
This article clarifies common misconceptions about load testing, defines it within performance testing, and provides practical strategies for test volume, load generators, scripting, think time, ramp-up/down, monitoring, diagnosis, and data analysis to ensure reliable performance assessments.
The article explains the distinct purposes and benefits of performance, stress, and load testing, showing how each practice helps identify bottlenecks, ensure stability under load, and improve overall software quality throughout the development lifecycle.
This article outlines a comprehensive internship training program for software testing engineers, covering onboarding rules, theory lessons, bug and test case management, tool usage, industry knowledge, career development, communication skills, assessment methods, and feedback processes to prepare interns for real‑world testing roles.
This article explains how to write robust end‑to‑end automated tests, emphasizes the importance of hermetic (sealed) testing environments, and provides practical guidelines, best‑practice recommendations, and considerations for maintaining reliable, fast, and maintainable test suites in complex web applications.
The article explains why unit tests should focus on verifying distinct behaviors rather than mirroring methods, advocating separate, focused tests that make cause‑and‑effect relationships obvious and improve code readability and maintainability.
This article explains why functional test automation is essential for modern agile and DevOps teams, outlines how to calculate its return on investment, and provides a detailed roadmap of testing strategies, team composition, and maintenance practices to reduce costs and improve software quality.
This article outlines practical quality assurance strategies—including outsourcing QA teams, integrating testing early in the development lifecycle, and adopting automation frameworks—to improve software quality, reduce costs, and support business growth in digital transformation initiatives.
This article explores how to assess the efficiency improvements brought by test automation, examines standards for successful automation, and debates whether bugs detected by automated tests should generate instant alerts or be manually verified before reaching the bug‑tracking system.
This guide outlines a six‑step framework for creating an effective test automation strategy, covering scope definition, methodology, risk analysis, environment setup, execution planning, and continuous review to prevent costly production bugs.
The article examines why basic functional testing jobs are dwindling, highlights growing opportunities in automation, performance, security, big‑data and AI testing, and offers a practical roadmap to help testers acquire new skills and advance toward higher‑salary roles.
The article explains what virtualization is, outlines its main types, and shows how it enables efficient software testing by consolidating servers, improving disaster recovery, saving time, increasing availability, reducing complexity, and protecting data, while also noting potential driver, memory, and performance issues.
Software testing demands efficient strategies, and this article explores four practical techniques—pairwise testing, clustering-based aggregation, greedy algorithms, and fuzzy logic—to dramatically reduce the number of test cases while maintaining coverage and improving testing speed.
This article outlines how QA engineers can maximize their impact throughout the pre‑testing, testing, and post‑testing phases of cross‑department projects by understanding system interactions, coordinating with stakeholders, designing comprehensive test cases, monitoring progress, and conducting thorough retrospectives to continuously improve delivery quality.
This page provides a curated collection of Chinese articles covering unit testing, white‑box testing, testing frameworks such as Spock, JUnit, Selenium, performance testing, and related technical and non‑code topics for software developers and testers.
White-box testing examines a program’s internal structure, code, and logic by creating and executing test cases that cover all paths, conditions, and statements, enhancing security, reliability, and code quality, while outlining its steps, techniques, examples, advantages, and drawbacks.
This article presents a curated list of fifteen essential books for software testers, covering foundational testing concepts, agile testing principles, practical BDD approaches, and DevOps methodologies, each accompanied by concise recommendation reasons to guide both beginners and experienced professionals.
The article describes IMVU’s lean‑startup‑inspired continuous deployment system, detailing how they achieve 50 daily releases through automated testing, Buildbot CI, a cluster‑immunity rollback script, rapid user feedback, and extensive QA practices that balance speed with quality.
Youku’s unified playback testing platform consolidates a modular automation framework, a comprehensive service chain, and a layered platform ecosystem to standardize workflows, support multiple device types, and provide transparent, real‑time monitoring, thereby reducing development complexity and paving the way for intelligent case recommendation and dynamic verification.
The article recounts a three‑month QA internship, describing how the author moved from theoretical test knowledge to hands‑on practices such as pre‑testing preparation, test case design, environment management, bug reporting, and personal growth within a collaborative team.
The article explains the shortcomings of traditional scripted testing in agile projects, introduces the test pyramid and exploratory testing concepts, clarifies how exploratory testing differs from random testing, and outlines practical Session‑Based Test Management techniques for effective agile quality assurance.
This article examines the key differences between manual and automated testing, covering time cost, acceptance testing, accuracy, regression testing, and project characteristics to help teams decide which approach best fits their software projects.
This collection provides a curated set of Chinese and English resources covering unit testing frameworks like Spock, JUnit, Selenium, performance testing tools, API testing, and related non‑technical articles, offering developers comprehensive guidance for software testing practices.
During the pandemic, Tencent Cloud University partnered with its TVP team to launch a free live course series led by senior DELL EMC architect Ru Bingsheng, teaching disruptive, agile software‑testing innovations for the UVCA era, while offering interactive Q&A, prizes, and TVP certification information.
The article outlines essential software testing practices, emphasizing comprehensive business understanding, thorough process knowledge, early and prioritized testing, collaborative test case reviews, post‑test summarization, responsibility, and the benefits of automation to improve quality and efficiency.
This page compiles a comprehensive collection of Chinese-language articles and resources covering software testing principles, automation strategies, DevOps integration, QA best practices, and related development topics, providing readers with curated links to deepen their understanding of testing methodologies and industry trends.
This article outlines the most frequent mistakes beginners make in test automation—from automating unnecessary modules and poorly defining scope to choosing the wrong tools, neglecting communication, ignoring ROI, over‑relying on open‑source projects, and trusting no‑code solutions—offering practical guidance to help avoid costly errors.
The article explores how reinforcement learning can be used to create a test robot that performs UI traversal, discussing the challenges of full automation, defining the MDP components, feature extraction methods, reward design, and suitable RL algorithms to improve testing coverage and efficiency.
The article explains the challenges of balancing sprint development with regression testing in agile projects and provides a step‑by‑step strategy—including information gathering, test scope definition, automation, and prioritization—to create a sustainable regression testing process that maintains quality and speed.
This guide outlines the key 2020 trends, essential automation and programming skills, recommended learning resources, and practical steps for test engineers to advance their careers, stay current with emerging technologies, and build a strong professional presence.
The article argues that software testing quality cannot be fully captured by quantitative metrics alone and should instead be guided by customer expectations, project goals, and OKR‑based priorities, emphasizing the need for thoughtful test case design and continuous improvement of tester skills.
The article explains various integration testing approaches—including Big Bang, Incremental, Bottom‑up, Top‑down, and Hybrid—and outlines practical best‑practice guidelines such as test ordering, separating test suites, thorough logging, and creating shared test plans for developers.
Integration testing verifies that individually tested software units work together as intended, bridging the gap between unit tests and system tests, and is a critical practice for DevOps teams to ensure cohesive, reliable applications.
The article explains how well‑crafted test cases—containing precise names, IDs, preconditions, steps, data, expected results, actual results, and defect links—reduce reliance on individual testers, aid defect reproduction, support automation, serve as training material, and act as long‑term evidence while warning against over‑detailing in time‑critical or ad‑hoc scenarios.
This article explains the fundamentals of black‑box and white‑box testing, outlines their functional, non‑functional, and regression variants, and shows how combining both approaches improves software reliability, security, and performance.
