This article explains how adopting continuous testing—by decentralizing test teams, clearly defining test types, and managing automated test data—enables faster feedback, higher quality releases, and smoother DevOps adoption, while highlighting practical steps and common pitfalls.
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 article outlines practical strategies for maintaining Selenium test automation, including keeping test cases simple, encouraging developer involvement, defining execution strategies, improving test stability, focusing on high‑return‑on‑investment scenarios, and using cloud services for efficient cross‑browser compatibility testing.
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.
When web applications become highly dynamic, traditional Selenium locators become fragile and costly to maintain, but leveraging AI and machine‑learning‑based object‑recognition frameworks can dramatically reduce maintenance overhead and accelerate test creation by intelligently adapting to UI changes.
This article outlines a systematic approach to evaluating test automation effectiveness by detailing twelve quantifiable metrics—from bug detection rates and execution stability to platform usage and ROI—while emphasizing the critical mindset of automation champions for successful adoption.
This article explains why Selenium test automation requires ongoing maintenance, outlines the two main maintenance scenarios—test failures and dependency changes—and provides practical guidance for developers and testers to efficiently support and sustain automated testing in agile environments.
This article explains agile testing principles, contrasts them with traditional waterfall testing, and details how the P1 project applied Scrum testing practices—short delivery cycles, daily stand‑ups, bug triage, continuous collaboration, technical excellence, and streamlined processes—to achieve rapid, high‑quality software releases.
This article explains why and how to implement parallel testing with Selenium, illustrating the massive time savings, broader test coverage, cost benefits, and integration with continuous integration pipelines through practical examples and step‑by‑step guidelines.
This article describes how Ctrip built a traffic replay platform that leverages ElasticSearch logs to automate both API and UI testing, enabling rapid regression, visual comparison, and continuous integration, ultimately reducing test effort and increasing release frequency.
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 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.
This article presents a practical guide to designing a usercenter module for API testing in Java, detailing a maintenance‑free data strategy, key automation principles, and a full code example that demonstrates user info retrieval, password modification, avatar upload, and feedback handling, with a Gitee repository link.
The Moonlight Box (JCASE) platform records production traffic and replays it in test environments to achieve fully automated, high‑coverage regression testing, reducing test data preparation effort and supporting online, offline, stress, and pre‑heat scenarios across large‑scale service architectures.
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.
This article ranks the seven most popular programming languages for test automation in 2020—Python, Java, JavaScript, C#, Ruby, PHP, and SmashTest—detailing their strengths, community support, and key frameworks to help you select the best language for your automation projects.
This article explains the fundamentals of unit testing, covering its definition, core concepts, essential principles, practical techniques such as mocking, and its role in test automation and continuous integration within modern agile development.
This article examines common pitfalls of test automation, critiques traditional framework‑only solutions, and details how the HAWK platform integrates automation frameworks, case‑set management, and a data factory with CI/CD to boost testing efficiency and product quality.
This article provides a comprehensive Q&A covering common misconceptions, recommended books, incremental vs. iterative development, test‑to‑dev ratios, suitable projects, DevOps differences, unit‑test ownership, workload estimation, bug handling, release criteria, test‑team organization, automation practices, and essential skills for effective agile testing.
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 explains how to use feature flags in a three‑tier microservice architecture, describing the need for both high‑level end‑to‑end tests and low‑level unit tests within CI/CD pipelines to ensure correct behavior when flags are on or off, while avoiding excessive test combinatorial explosion.
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 tutorial walks through essential Selenium WebDriver techniques in Python, covering driver path configuration, capturing full and partial screenshots, page refresh methods, opening new tabs, cropping images with Pillow, executing JavaScript, and retrieving script results, all with clear code examples.
This tutorial explains how to use Selenium's built‑in PageFactory to implement the Page Object pattern, defines a TodoMVC API, provides JUnit 5 test examples, shows a concrete Page implementation with @FindBy annotations, discusses additional locator annotations, element lookup timing, and demonstrates running the tests from the command line.
This article compiles practical guidelines for software testers, covering comprehensive business understanding, end‑to‑end workflow awareness, common developer pitfalls, early testing of new features, prioritizing complex requirements, verification and negative testing, test case preparation, post‑test reviews, responsibility, and the benefits of test automation.
This article explains the motivation behind building ITest, a unified API testing platform, details its architecture, key features such as Swagger import, parameterization, assertions, signing, and CI/CD integration, and summarizes the benefits it brings to development and testing teams.
The article outlines practical criteria for choosing which test cases to automate, emphasizing repeatability, difficulty, core workflow importance, extensive data requirements, risk assessment, and the value of regression, smoke, and sanity testing to improve software quality and reduce testing costs.
This article explains what APIs and API testing are, outlines various test case types and testing methods, compares API testing with unit testing, lists best practices, common error types, recommended tools, and challenges faced when testing APIs in software development.
This article provides a comprehensive overview of the MySQL Test Run (MTR) framework, detailing its two-part architecture consisting of Perl scripts for control flow and C++ binaries for test execution, along with the complete execution process and framework design.
The article outlines the advantages of automated testing—including 24/7 execution, efficient regression, reusability, time and cost savings, early defect detection, reduced manual effort, increased coverage, and monitoring—while acknowledging its limitations and the continued need for manual testing.
This article outlines practical criteria for selecting test cases to automate versus keeping them manual, covering business‑critical paths, repeatability, data‑driven scenarios, performance needs, and situations where automation is not worthwhile.
The article reviews Selenium 4.0 Alpha, explaining why the release matters for test automation, detailing major updates such as W3C WebDriver standardization, the revamped Selenium IDE, an easier‑to‑use Grid, enhanced observability, and refreshed documentation, and highlights the impact on both code‑centric and no‑code testing workflows.
This article compares three popular Python test automation frameworks—Robot Framework, pytest, and unittest—detailing their prerequisites, key advantages, drawbacks, and ideal use cases to help developers choose the most suitable tool for their testing needs.
The article describes how Ctrip Ticket's front‑end team introduced Behavior‑Driven Development (BDD) using Cucumber and the Macaca‑based MEC framework to unify requirements, automate testing, reduce manual effort, and achieve over 90% UI test coverage while cutting integration costs by 75%.
This article demonstrates how to automate e‑commerce test data creation by retrieving schema information with SQLAlchemy ORM, defining mapping classes, generating realistic data using Faker, and submitting it via HTTP requests with the Requests library, covering database interactions, data assembly, and API communication.
This guide explains how to evaluate the return on investment of Selenium‑based cross‑browser test automation by defining key metrics, outlining calculation formulas, discussing common pitfalls, and offering practical steps to maximize efficiency, coverage, and risk reduction.
This article introduces Python’s built‑in unittest framework, outlining its lightweight advantages, core components such as TestCase, TestSuite, TestRunner and TestLoader, and demonstrates a complete automation workflow from Excel‑based test data preparation to generating HTML test reports with HTMLTestRunnerNew.
This guide explains why automated testing is overtaking manual testing, outlines the main categories of automation tools, and provides practical criteria—such as platform support, adoption ease, scripting flexibility, integration, reporting, and licensing—to help teams select the most suitable solution for their CI/CD and DevOps workflows.
The article explains the distinction between automated testing and test automation, why test automation is crucial for continuous testing in DevOps pipelines, and outlines practical steps and tools needed to implement effective test automation for maintaining quality and speed in modern software delivery.
The article explains the distinction between automated testing and test automation, highlights why test automation is essential for continuous testing and DevOps pipelines, and outlines practical steps and requirements for implementing effective test automation in modern software delivery processes.
The article examines the frequent reasons test automation projects collapse—from unrealistic 100% automation expectations and poor management visibility to inadequate manual testing, tool mis‑selection, false positives, and lack of collaboration—offering practical guidance to improve automation success.
This article outlines the six-stage automated testing lifecycle methodology—from defining automation scope and selecting tools, through test planning, environment setup, script development, execution, and result analysis—providing practical guidance for improving software quality with efficient, resource‑conscious testing practices.
The article explains the benefits and limitations of test automation, outlines scenarios where manual testing remains essential, and provides practical guidance on deciding what to automate, why to automate, and how to implement automation effectively.
This article explains how to build a Java wrapper that loads and runs Groovy test scripts at runtime, covering classloader nuances, reflection-like execution, file discovery, method filtering, and provides a complete code example for a custom test framework.
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 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.
The article demonstrates a simple Java ThreadTest class that enables concurrent database updates during Android UIAutomator and Selenium‑Java test cases, showing how to control execution with key flags, integrate the thread into test methods, and optionally use join() to avoid exceptions.
This article presents a comprehensive data quality model derived from ISO 9126, maps its characteristics to data testing, outlines practical testing methods and tool requirements, and demonstrates how to integrate quality checks into the data development lifecycle for reliable, efficient big‑data pipelines.
Microsoft’s Azure DevOps team dramatically improved engineering efficiency by adopting a shift‑left testing strategy, replacing thousands of legacy functional tests with fast, reliable unit and integration tests, establishing six testing principles, a tiered test pyramid, and data‑driven metrics that now enable tens of thousands of daily releases.
This article introduces HttpRunner, covering supported platforms, installation commands, key features such as parameter extraction, global configuration, variable handling, data-driven testing, report generation, and practical steps for converting HAR files to test cases and executing them with hrun.
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.
The article introduces a comparative test platform for financial core systems that automates regression testing of batch jobs, dramatically reducing test cycles from days to under one, while ensuring billing calculations remain accurate across evolving business scenarios.
This guide walks through installing Python, pip, RobotFramework and its HTTP library, then demonstrates a complete RobotFramework test case that defines variables, creates an HTTP context, handles error scenarios, and validates response status and body content.
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 provides a comprehensive overview of the daily work of the Shanghai R&D Center Test Team at Dada-Jingdong to Home, covering project quality assurance, automation, tool construction, and quality culture building.
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 details the design, evolution, and implementation of an online test‑monitoring platform that transforms CI/CD pipelines into proactive alerting systems, covering the initial Spring‑based prototype, its shortcomings, the 2.0 configurable and visual redesign, plugin architecture, and future distributed deployment plans.
The article discusses how embracing speed and flexible configuration in QA, exemplified by the Beetle platform’s interface testing workflow, can improve project efficiency, enable unified automated testing, and integrate continuous integration, while emphasizing that tools alone cannot guarantee test quality.
This article describes how a hotel testing team integrated white‑box testing—code review and static analysis—into fast‑paced agile workflows, detailing the exploration timeline, typical functional testing challenges, three concrete bug‑finding case studies, measurable quality improvements, and practical promotion guidelines.
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 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.
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.
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.
This article guides readers through setting up a Python environment, installing BeautifulReport, organizing test projects, and combining unittest with multithreading to produce a single, polished HTML test report while addressing common pitfalls and configuration issues.
Facing tight resources, Shanghai’s takeaway QA team adopted Ruby to craft two automation frameworks—Coral‑API for interface testing with a DSL, code generation and extensibility, and Coral‑APP for UI testing using Appium and Cucumber—while also building a Rails‑based quality management system that cut regression time by over half, trained new Ruby users, and uncovered version‑specific bugs through CI integration.
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 describes how a Python‑based nosetests framework was extended with a Master‑Runner architecture and pyzmq messaging to run test cases in parallel across multiple runners, reducing execution time from over ten minutes to just a few minutes and enabling fast feedback in CI/CD pipelines.
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.
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.
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 guide shows how to use Selenium WebDriver in Java to locate web elements by name, id, tag name, class name, link text, and partial link text, providing complete example code for each method to interact with input fields and links on a test page.
Despite widespread reliance on manual UI testing, this article details how the author’s team built an Espresso‑based test platform that achieves 80‑90% functional coverage, introduces the ETP design, explains single‑page testing, test flows, and shares practical solutions to common Espresso pitfalls.
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 explains what APIs are, why functional API testing is essential, outlines the test pyramid, discusses the advantages of API tests such as higher coverage and faster feedback, and provides practical guidance on tools, test design, and CI integration.
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.
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 explains how Google test engineers tackle the challenges of maintaining and upgrading legacy systems by redesigning test infrastructure, reducing reliance on fragile end‑to‑end tests, and adopting lightweight, mock‑driven test cases that dramatically speed up verification while preserving defect detection quality.
The sixth Meituan‑Dianping technical salon explored building an O2O quality system by showcasing internal testing solutions—including full‑link online pressure testing, the Spider mobile compatibility tool, Didi’s mock decoupling framework, and the Conan performance‑data platform—detailing their methods, architectures, and impact on testing efficiency.
This article details Qiniu's evolution from no testing to a comprehensive front‑end testing strategy using Selenium, Karma, Jasmine, AngularJS, and Sinon, covering early challenges, unit‑test design, tool configuration, mock data handling, and the tangible benefits for code quality and maintenance.
