In microservice architectures, end‑to‑end tests often become flaky, slow, and untrustworthy because the assumptions of a stable, deterministic system clash with the reality of distributed, asynchronous services, leading to noisy failures, maintenance overhead, and delayed feedback.
This article outlines a comprehensive testing strategy for the movie-web application, covering unit tests for utility functions and state management, component tests with React Testing Library, integration tests using MSW, and a proposed end‑to‑end workflow with Cypress or Playwright, plus CI/CD automation and coverage goals.
This article explains how comprehensive testing—from early shift‑left practices and lifecycle coverage to automated unit, integration, and end‑to‑end tests—ensures software quality, reduces costs, and supports rapid development, illustrated with real‑world case studies and practical design techniques.
YouZan implemented a BackstopJS‑based visual regression testing platform that automatically compares pre‑release and production pages, managing cases, scenarios, tags and selectors, which now runs over 1,000 tests, saves roughly 300 person‑days per year, has uncovered more than 100 e‑commerce issues, and is being extended to mini‑programs, React/Vue component checks, and traffic‑playback UI monitoring.
This article compares two E2E test case generation approaches—recording via Playwright’s codegen and behavior‑driven development (BDD) using Gherkin—detailing their principles, code examples, selector handling, DSL design, and the trade‑offs in flexibility, difficulty, and readability for web testing.
This article explains the overall architecture of Chrome extensions, how to create popup, DevTools, and content scripts using React or Vue, configure manifest.json, set up multi‑entry Webpack builds, debug each component, and perform end‑to‑end testing with Puppeteer and Xvfb for CI environments.
The article describes how to build an H5 page Experience Checkpoint service that automatically runs headless‑browser scripts to detect critical (P0) and potential (P1) UX issues—such as large media, privacy leaks, or slow APIs—by integrating data providers, page inspectors, and reporters into an existing inspection system, exposing a task‑creation API, and delivering detailed HTML reports via Feishu.
This article explains how to determine the right amount of testing for a software product by providing evaluation criteria, a step‑by‑step testing strategy—including recording processes, unit, integration and end‑to‑end tests—coverage types, tools, and how to incorporate field feedback for continuous improvement.
This article explains how to create end‑to‑end visual regression tests for Canvas‑based tools by capturing reference screenshots with a headless browser, comparing them pixel‑by‑pixel using pixelmatch, and visualizing differences, complete with code examples and best‑practice recommendations.
The article details how the Tongtian Tower team adopted Puppeteer for end‑to‑end testing of their web‑based build system, covering technology selection, core concepts, API usage, project architecture, practical challenges, and the measurable efficiency gains achieved through automation.
The article explains why many microservice projects struggle with truly independent deployment, shows how centralized E2E tests create a deployment bottleneck, and proposes inline E2E tests and contract testing as practical solutions to preserve independent delivery while ensuring quality.
This article introduces Nightwatch.js, a Node.js‑based end‑to‑end testing framework for web and app testing, explains why the author switched from Java‑Selenium‑TestNG to Nightwatch.js, and outlines its key features such as simple syntax, built‑in runner, Selenium integration, cloud support, CI reporting, and extensibility.
