From Copy-Paste to a Specification-Driven Test Engine: Reusing Behavior in Large Web Systems

说明与用途

在大型 Web 应用中，每个页面的自动化测试往往会重复相同的行为，导致测试数量和维护成本膨胀。本文提出一种基于规范的测试方法：为每个页面编写结构化规范，随后根据页面功能使用共享的 Playwright 测试套件。该方法将测试数量和代码量降低了约 80%，并使少量共享测试能够覆盖超过千个页面特定场景。

问题

Automated test suites for each page in large web applications duplicate identical behavior, inflating test count and maintenance effort.

结果

The approach cut test code and count by roughly 80%, enabling a small set of reusable behavior suites to cover over a thousand page-specific scenarios while maintaining explicit coverage models.

工作流

• Define a structured page specification with identity, capabilities, column metadata, and setup requirements.
• Validate the specification for readiness.
• Use a plan builder to convert the specification into a test plan that lists applicable reusable behaviors.
• Register tests in shared Playwright suites based on the plan, creating only the scenarios that match the page’s capabilities.
• Execute tests via Playwright runner; report results with standard Playwright tooling.
• Iterate: update specifications when page capabilities change, automatically adjusting test coverage.

证据

In the project described here, this approach reduced the test count by approximately 80% and the overall test-layer code by approximately 79%.

来源

Each page is represented by a structured specification. A test engine interprets that specification, builds a test plan, and uses shared Playwright suites to verify the applicable behaviors.

来源

A page specification is a structured description of a page. It contains information such as: Page identity, Supported capabilities, Column metadata, Navigation and setup requirements.

来源