brunoboto96/scenescout
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
🔭 Your coding agent, turned into a QA tester for any web app. Finds what is broken and shows you the proof: pictures, replays, journey videos and test reports.
概要
Works with Claude Code · Cursor · VS Code (Copilot) · Codex CLI · Gemini CLI · Copilot CLI · Windsurf · any MCP client Scripted end-to-end tests answer one question: does this exact flow still work? They say nothing about the rest of the app. SceneScout lets the agent you already use explore a running web app like a curious, thorough tester. It clicks, fills forms, switches roles and calls the API behind a hidden button, then writes a report of what is and what could be , with a picture and evidence for every line. Try it on any app you are allowed to test. No account, no API key, no setup: A real run against the small demo app in this repository, which has bugs planted on purpose. The two you can see are outlined: It filed twelve findings. A few from the report: 2× click fired the same state-changing request 2× (POST /api/orders) POST /api/orders/1037/approve 200 as clerk: the button was hidden, the server did not agree. GET /api/orders?
README
以下は原文 README の抜粋です。原文を見る。
Scripted end-to-end tests answer one question: does this exact flow still work? They say nothing about the rest of the app. SceneScout lets the agent you already use explore a running web app like a curious, thorough tester. It clicks, fills forms, switches roles and calls the API behind a hidden button, then writes a report of what is broken and what could be better, with a picture and evidence for every line.
Try it on any app you are allowed to test. No account, no API key, no setup:
npx -y scenescout http://localhost:3000
flowchart LR
A["🧠 Your coding agentClaude Code, Cursor, Copilot…"] -- MCP --> S["🔭 SceneScoutbrowser · checks · memory"]
S --> App["🌐 Your running app"]
S --> R["📋 Reportplain words + pictures"]
S --> E["🎬 Evidencereplay, videos, test report"]
👥 Who it’s for
| 🛠️ Developers | 🧑💼 QA, product and non-technical teams |
|---|---|
Findings with the request that failed (GET /api/orders?status=archived → 500), the steps, and a Playwright regression-test skeleton |
Each problem in plain words first: what was done, what was expected, what happened, and a picture of the page |
| Next to the source, the file behind the bug and a likely fix | Visible problems shown, not described: a covered button, a broken image, text too faint to read |
| A deterministic gate for pull requests, with SARIF for code scanning | Journeys recorded step by step, as frames and video, so a pass is something you can watch |
| Runs from your editor’s agent, or unattended in CI | A test report laid out by your template, with expected and actual results, deviations and blank sign-off rows |
🐛 What it catches
A real run against the small demo app in this repository, which has bugs planted on purpose. The two you can see are outlined:
インストール
npx -y scenescout http://localhost:3000