
🔭 你的编码代理,变成了任何网页应用的质量测试员。找出故障并向你展示证据:图片、回放、旅程视频和测试报告。
概览
可使用 Claude 代码 ·光标 ·VS 代码(副驾驶)·Codex CLI ·双子座 CLI ·副驾驶 CLI ·风帆冲浪 ·任何 MCP 客户端 脚本化的端到端测试回答了一个问题:这种流程现在还能正常工作吗?它们对应用的其他部分没有任何说明。SceneScout 让你已经用的代理像一个好奇、细致的测试员一样,探索正在运行的网页应用。它点击、填写表单、切换角色,并在隐藏按钮后调用 API,然后写一份关于现有和可能发生的报告,每行都有图片和证据。 试试你允许测试的任何应用。没有账户,没有API密钥,没有设置: 这真是与这个仓库里那个小型演示应用的较量,后者故意植入了漏洞。你看到的两个应用概述如下: 该委员会提交了十二项结论。报告中摘录了几项: 2×点击触发了同样的状态变化请求 2×(POST /api/orders) POST /api/orders/1037/approve 200 作为职员:按钮被隐藏了,服务器不同意。获取 /api/orders?
概述(AI 翻译)
你的编码代理,变成了任何网页应用的探索性质量保证测试员。
可使用 Claude 代码 ·光标 ·VS 代码(副驾驶)·Codex CLI ·双子座 CLI ·副驾驶 CLI ·风帆冲浪 ·任何 MCP 客户端
网站 ·📖指南 ·🐛它捕捉的内容 ·🎬带证据的质量保证 ·🚀开始 ·🚦 CI ·🔒安全 ·📚文档 🌐
脚本化的端到端测试回答了一个问题:这种流程现在还能正常吗? 它们对应用的其他部分没有任何说明。SceneScout 让你已经用的代理像一个好奇、细致的测试员一样,探索正在运行的网页应用。它点击、填写表单、切换角色,并在隐藏按钮后调用 API,然后写一份报告,说明哪些是“坏的”,哪些是可以做得更好**,每行都有图片和证据。
试试你允许测试的任何应用。没有账户,没有API密钥,没有设置:
👥 这是给谁的
|🛠️ 开发者🧑 💼质量保证、产品及非技术团队
|—|—|
|发现,包括失败请求(GET /api/orders?status=archived → 500)、步骤,以及Playwright回归测试骨架|每个问题先用简明的语言说明:做了什么,预期了什么,发生了什么,以及页面图片 |
本页由 AI 翻译,技术细节请以原文为准。
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