Back to Details

workbench-browser-proofshot-qa

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Workbench Browser Proofshot QA

Workbench Browser Proofshot QA

Use this skill for browser-based verification, Playwright checks, proof screenshots, local web app dogfooding, and reproducible UI evidence.
使用该skill进行基于浏览器的验证、Playwright检查、验证截图、本地Web应用dogfooding，以及可复现的UI验证证据。

Browser Verification Loop

浏览器验证流程

  1. Start or identify the real app URL.
  2. Record browser, viewport, account/auth state, and build/commit when available.
  3. Exercise the user workflow, not only page load.
  4. Capture screenshots or trace artifacts for states that matter.
  5. Check console errors, failed network requests, obvious layout breakage, and final persisted state.
  6. Report exact repro steps and evidence paths.
  1. 启动或确定真实应用的URL。
  2. 记录浏览器信息、视口、账户/认证状态，以及可用时的构建/提交版本。
  3. 执行用户工作流，而非仅检查页面加载。
  4. 捕获关键状态的截图或追踪工件。
  5. 检查控制台错误、失败的网络请求、明显的布局损坏，以及最终的持久化状态。
  6. 报告准确的复现步骤和证据路径。

Boundaries

边界规则

  • Do not edit code during report-only QA unless explicitly assigned.
  • Do not treat a static screenshot as proof that a workflow works.
  • Do not rely on cached authenticated state without saying so.
  • Do not include private data in screenshots or copied logs.
  • 除非明确指派，否则在仅报告的QA过程中不得编辑代码。
  • 不得将静态截图视为工作流正常运行的证据。
  • 不得依赖缓存的认证状态而不加以说明。
  • 不得在截图或复制的日志中包含私有数据。

Output Contract

输出约定

Return:
  • BROWSER_VERDICT
    : PASS / FLAG / BLOCK.
  • RUN
    : URL, viewport, browser/tool, commit/build if known.
  • STEPS
    : concise repro or verification path.
  • EVIDENCE
    : screenshot/trace/log paths.
  • FINDINGS
    : ordered by severity.
  • FOLLOW-UP
    : smallest fix or re-test needed.
返回内容需包含：
  • BROWSER_VERDICT
    : PASS / FLAG / BLOCK.
  • RUN
    : URL、视口、浏览器/工具、已知的提交/构建版本。
  • STEPS
    : 简洁的复现或验证路径。
  • EVIDENCE
    : 截图/追踪/日志路径。
  • FINDINGS
    : 按严重程度排序的问题。
  • FOLLOW-UP
    : 所需的最小修复或重新测试内容。