In the era of knowledge sharing, discover 转转QA from a new perspective.
This article shares practical habits and a structured five‑stage process for creating comprehensive test plans for an Order Management System, covering pre‑review preparation, design‑phase collaboration, post‑design verification, final review, and continuous improvement to ensure quality and alignment with business goals.
This article analyzes the challenges of traditional system load testing, proposes an iterative testing workflow that enhances service and environment stability, reduces manpower and timeliness costs, aligns testing with business needs, and outlines the evolution of a full‑process testing model with practical feedback.
This article explains why and how to use asynchronous processing in Servlet 3.0 and Spring MVC, compares four implementation approaches (no return value, Callable, WebAsyncTask, DeferredResult), provides detailed code examples, and demonstrates a real‑world use case for decoupling long‑running tasks.
This article details how Zhuanzhuan’s testing environment progressed from a handful of static machines to a Docker‑driven dynamic‑and‑stable architecture, addressing resource shortages, stability issues, and operational inefficiencies through IP routing, tag routing, and extensive automation, ultimately achieving significant reductions in resource usage, deployment time, and user‑reported problems.
This article details Zhaozhuan's three‑generation test environment governance evolution—starting with physical isolation, moving to automatic IP‑label traffic routing, and finally manual tag‑based routing—highlighting architectural changes, deployment processes, advantages, drawbacks, and supporting tools such as distributed tracing and debugging utilities.
This article explains how to design comprehensive test cases for offline store applications by reviewing requirement documents, applying testing theories, using software quality models, and addressing new features, existing feature iterations, technical refactoring, and statistical reporting requirements to ensure robust quality assurance.
This article explains how Aspect‑Oriented Programming (AOP) was introduced into a data construction platform to address high development effort, strong business coupling, and maintenance difficulty by isolating cross‑cutting concerns such as logging, thereby improving modularity, development speed, and code maintainability.
This article shares a two‑week experience of quickly learning and testing the after‑sales business for a QA engineer, outlining preparation steps, core B2C after‑sales workflow, demand analysis, and practical testing strategies for cross‑business tasks.
This article introduces JVM‑Sandbox, explains its non‑intrusive AOP capabilities, and provides a step‑by‑step tutorial on installing the sandbox, loading custom modules, performing code enhancement via instrumentation, and testing exception injection in a Java service.
This article outlines how QA can proactively join technical design reviews, detailing the required documentation, preparation steps, thinking methods, impact assessment, and testability improvements to ensure higher delivery quality and better collaboration among product, development, and testing teams.
