YAML-Based Testing: A New Approach to E2E

End-to-end testing has a maintenance problem. Traditional test scripts are brittle, verbose, and tightly coupled to the DOM. A single UI refactor can break dozens of tests that were working perfectly the day before. Teams end up spending more time fixing tests than writing new ones. YAML-based testing takes a different approach. Instead of writing procedural scripts that describe how to interact with elements, you write declarative files that describe what you want to test. The execution engine handles the how. This is not a theoretical concept — Shiplight uses YAML as its native test format, and the approach fundamentally changes how teams think about E2E test maintenance. Why YAML for Testing The choice of YAML is deliberate. It solves three problems that plague traditional E2E test scripts. Readability. A YAML test file reads like a checklist of user actions. Anyone on the team — developers, QA engineers, product managers — can read a YAML test and understand what it covers. Playwri