playwright-generate-test

Playwright test generation from a text scenario converts your described UI workflow into deterministic TypeScript code. It executes required Playwright MCP steps sequentially based on message history to produce a passing @playwright/test file.

Automating end-to-end UI validation without manual coding is possible by converting scenarios into TypeScript tests. The skill handles tool-driven step completion and iteratively executes the generated code until the test passes.

The best way to ensure generated Playwright E2E tests pass is through iterative verification. The process executes the generated test file, checks the results, and iterates on the code until deterministic passing behavior is achieved.

Test generation requires the Playwright MCP environment to run sequential steps before producing code. It uses the standard @playwright/test framework and saves the final TypeScript output directly to your tests directory.

Converting a described user workflow into a deterministic Playwright test involves guiding the agent through required MCP steps sequentially. It produces aligned TypeScript code adhering to Playwright Test conventions for reliable validation.

Limitations of generating E2E tests from scenarios include relying on sequential Playwright MCP step execution to build message history. The generated TypeScript test targets automated UI validation and may require multiple iterations to pass.