Building a Transpiler to Migrate over 4,000 Tests to Playwright Preface I...
Building a Transpiler to Migrate over 4,000 Tests to Playwright
Preface
I migrated a large existing test suite to a new framework. Some of the same ideas and techniques may be useful for migrations that seem too large to start.
Background
Recently I joined an internal team at my current place of work with the goal of improving the QA pipeline. The team supported and maintained a chatbot. It was a complex AWS Connect setup: hundreds of flows, free text input and dynamic Lambda functionality.
I joined a project with an existing Playwright E2E test suite, 38 spec files, ~165 tests, around...
How I used Cursor, Playwright MCP, and Playwright CLI to build real automation for...
A production-ready Playwright CI/CD pipeline — GitHub Actions, test sharding across machines, browser matrix, Docker for…
Replace Postman with Playwright's request context. Schema validation, auth token flows, GraphQL testing, and chaining API setup…
Test real-time collaboration, role-based permissions, and multi-tab flows in Playwright. Two users. One test. The scenarios most…
Stop using console.log to debug Playwright failures. Master Trace Viewer, Playwright Inspector, VS Code integration, and…
