Testing Layer Strategy Model: Design, Issues, and Practical Implementation

In the context of digital transformation, improving R&D efficiency while maintaining quality is a key concern; software testing, especially the test layering strategy, plays a crucial role. The article explains that a test layering strategy is part of the overall test strategy, focusing on how testing methods are chosen based on code architecture layers.

The author identifies three typical problems teams face: lack of a unified understanding of test layers, missing top‑level design that leads to fragmented testing efforts, and a gap between the strategy and actual daily work.

A practical model is proposed, using two dimensions—vertical (testability) and horizontal (quality risk)—to place a system into one of four quadrants. Each quadrant (Ideal, Legacy, Core, Legacy‑Core) receives specific test‑layering recommendations, ranging from the classic testing pyramid to inverted‑pyramid or trapezoidal approaches.

The model’s evolution follows two stages: first, align current practices with the recommended strategy for the system’s quadrant; second, improve testability and reduce quality risk to move the system into a more favorable quadrant.

Implementation involves four steps: customizing the model’s factors, conducting research and scoring, creating an improvement plan, and executing the plan. Real‑world case studies illustrate how teams assess their current state, select appropriate test layers (e.g., adding unit and API tests for a backend‑only system), and iteratively refine the strategy.

Finally, the article concludes that the test layering model helps teams visualize top‑level design, identify optimization points, and integrate improvement actions with technical debt management, thereby achieving higher test efficiency and cost‑effectiveness.