I build web apps with coding agents and wanted a clearer answer after each change: which routes still work, and which ones regressed? vibe-testing scans the project, runs browser checks with Playwright, and writes an HTML report with screenshots. On the next run it compares the results and marks fixes and regressions. It works as an MCP server in coding editors or as a CLI. The tool is MIT licensed and makes no LLM calls of its own. To try it in a web app: `npx vibe-testing@latest init` I would value feedback from builders testing a real app change this week. Where did setup get in the way? What did the report miss? I can use those answers to improve it. Site: https://vibetesting.tfgstudio.com/ Code: https://github.com/AishwaryShrivastav/vibe-testing   submitted by   /u/AishwaryShrivastava [link]   [comments]