--- title: "Vibe testing with Playwright" url: https://daily.dev/posts/vibe-testing-with-playwright-bay6cupo6 source_url: https://timdeschryver.dev/blog/vibe-testing-with-playwright type: article source: "Tim Deschryver" author: "Tim Deschryver" published: 2026-05-31T07:47:13.636Z updated: 2026-06-01T04:01:41.385Z tags: ["github", "mcp"] reading_time: 9 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Vibe testing with Playwright **[Tim Deschryver](https://daily.dev/sources/timdeschryver)** · [@timdeschryver](https://daily.dev/timdeschryver) · 9 min read · 0 upvotes · 0 comments ## Summary An exploration of Playwright's AI capabilities using the Playwright MCP server and GitHub Copilot agent mode to automatically generate end-to-end tests. The author navigates to their blog, prompts Copilot to write tests, and evaluates the quality of the generated test cases. Most tests pass on the first run, with Claude 3.7 producing well-structured tests using best practices like getByRole and toBeVisible. For failing tests, Playwright's new 'copy as prompt' feature lets you paste the error, ARIA snapshot, and test code directly into Copilot chat to get a fix. The overall verdict is promising: AI-generated tests are a solid starting point, especially for onboarding teams to Playwright or bootstrapping test coverage for new features. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#github](https://daily.dev/tags/github), [#mcp](https://daily.dev/tags/mcp) [View this post on daily.dev](https://daily.dev/posts/vibe-testing-with-playwright-bay6cupo6)