Simon Willison’s Weblog

Subscribe

Guides > Agentic Engineering Patterns > Agentic manual testing

Changes to Agentic manual testing

March 6, 2026, 5:44 a.m.

Draft status changed from draft to published.

March 6, 2026, 5:43 a.m.

Body

--- +++ @@ -48,7 +48,7 @@ Historically these have been difficult to test from code, but the past decade has seen notable improvements in systems for automating real web browsers. Running a real Chrome or Firefox or Safari browser against an application can uncover all sorts of interesting problems in a realistic setting. -The coding agents know how to use these tools extremely well. +Coding agents know how to use these tools extremely well. The most powerful of these today is **[Playwright](https://playwright.dev/)**, an open source library developed by Microsoft. Playwright offers a full-featured API with bindings in multiple popular programming languages and can automate any of the popular browser engines.

March 6, 2026, 5:43 a.m.

Body

--- +++ @@ -50,7 +50,7 @@ The coding agents know how to use these tools extremely well. -The most powerful of these today is **Playwright**, an open source library developed by Microsoft. Playwright offers a full-featured API with bindings in multiple popular programming languages and can automate any of the popular browser engines. +The most powerful of these today is **[Playwright](https://playwright.dev/)**, an open source library developed by Microsoft. Playwright offers a full-featured API with bindings in multiple popular programming languages and can automate any of the popular browser engines. Simply telling your agent to "test that with Playwright" may be enough. The agent can then select the language binding that makes the most sense, or use Playwright's default CLI tool.

March 6, 2026, 5:41 a.m.

Initial version.