{"id":90624,"date":"2025-09-05T09:00:00","date_gmt":"2025-09-05T16:00:00","guid":{"rendered":"https:\/\/github.blog\/?p=90624"},"modified":"2025-09-05T08:23:52","modified_gmt":"2025-09-05T15:23:52","slug":"how-to-debug-a-web-app-with-playwright-mcp-and-github-copilot","status":"publish","type":"post","link":"https:\/\/github.blog\/ai-and-ml\/github-copilot\/how-to-debug-a-web-app-with-playwright-mcp-and-github-copilot\/","title":{"rendered":"How to debug a web app with Playwright MCP and GitHub Copilot"},"content":{"rendered":"\n

I know it can feel like a unicorn, but most bug reports do, in fact, contain steps to reproduce the error (or repro steps). As wonderful as it is to have those, the process of walking through and validating everything is still tedious. In a perfect world, we’d have end-to-end or acceptance tests that could automate the process. Sadly, many projects lack robust testing.<\/p>\n\n\n\n

Fortunately, GitHub Copilot with the help of the Playwright Model Context Protocol (MCP) server can automate that entire process.<\/p>\n\n\n\n

\n\n\t\t

\n\t\t\t