原文核对：2026-10-13 · 中文正文 · 英文提示词与演示
场景定位
使用 Computer Use 验证关键流程、发现问题，并交付缺陷报告。
- 难度
- 中级
- 时间跨度
- 30 分钟
适合用于
- 发布前验证真实用户流程的团队。
- 需要严重程度、复现步骤和简明分诊摘要的 QA 流程。
起步提示词
英文原文 · 可复制后按实际材料修改
@Computer Test my app in [environment].
Test these flows:
- [hero use case 1]
- [hero use case 2]
- [hero use case 3]
For every bug you find, include:
- repro steps
- expected result
- actual result
- severity
Keep going past non-blocking issues and end with a short triage summary.简介
Computer Use 能看到界面、点击流程、填写字段并记录失败，适合在真实用户路径中发现功能缺陷和 UI 问题。
明确测试环境、重点流程和期望报告格式。
使用步骤
- 安装 Computer Use 插件。
- 指定要测试的应用、构建版本或环境。
- 列出最重要的流程或核心场景。
- 要求结构化报告，便于分诊和交接。
可以给出宽泛要求：
- @Computer 测试我的应用，找出主要问题并给我一份报告。
也可以更明确：
- @Computer 在 staging 测试我的应用，覆盖注册、邀请队友和升级计费；为每个缺陷记录复现步骤、预期结果、实际结果和严重程度。
如果仓库已有测试计划文件，请上传或指出位置，以便沿用既有流程。
实用建议
明确准备条件
提前说明影响流程的账号状态、测试数据、功能开关和环境，明确测试本地、staging 还是近似生产行为。
指定关注的问题类型
说明重点是功能故障、布局、令人困惑的文案、视觉回归，还是全部。
决定何时停止或继续
如果遇到一个阻断问题就应结束，请明确说明；否则要求继续检查其余流程，收集非阻断问题后再汇总。
后续操作
在同一对话中要求修复某个缺陷、整理为 Linear 或 GitHub 草稿，或将下一轮聚焦某条失败流程。
提示词示例
执行结构化 QA
官方提示词
英文原文 · 可复制后按实际材料修改
@Computer Test my app in [environment].
Test these flows:
- [hero use case 1]
- [hero use case 2]
- [hero use case 3]
For every bug you find, include:
- repro steps
- expected result
- actual result
- severity
Keep going past non-blocking issues and end with a short triage summary.展开英文原文对照
Use Computer Use to exercise key flows, catch issues, and finish with a bug report.
Introduction
Computer Use is a strong fit for QA passes because it can see the interface, click through flows, type into fields, and record what fails. That makes it useful for catching both functional bugs and UI issues across realistic user journeys.
The key is to tell Codex what environment to test, which flows matter most, and what kind of report you want back.
How to use
- Install the Computer Use plugin.
- Tell Codex which app, build, or environment to test.
- Name the flows or hero use cases you care about most.
- Ask for a structured report so the output is easy to triage or hand off.
You can keep this broad:
- @Computer Test my app. Find any major issues and give me a report.
Or make it more explicit:
- @Computer Test my app in staging. Cover signup, invite a teammate, and upgrade billing. Log every bug with repro steps, expected result, actual result, and severity.
If you already maintain a test-plan file in the repo, attach it to the chat or point Codex at it so the QA pass follows your existing flows.
Practical tips
Be explicit about setup
If account state, test data, feature flags, or environment choice affect the flow, include that up front. Codex will produce much better results when it knows whether it is testing local, staging, or production-like behavior.
Name the issue types you care about
Call out whether you want Codex to focus on broken functionality, layout issues, confusing copy, visual regressions, or all of the above.
Decide whether to stop or continue
If one blocking issue should end the run, say so. Otherwise, tell Codex to continue through the rest of the flow and collect all non-blocking issues before it summarizes.
Good follow-ups
After the QA pass, keep the same chat open and ask Codex to fix one of the bugs it found, turn the findings into Linear or GitHub-ready drafts, or narrow the next pass to one specific failing flow.
Suggested prompt
Run a Structured QA Pass
官方提示词
英文原文 · 可复制后按实际材料修改
@Computer Test my app in [environment].
Test these flows:
- [hero use case 1]
- [hero use case 2]
- [hero use case 3]
For every bug you find, include:
- repro steps
- expected result
- actual result
- severity
Keep going past non-blocking issues and end with a short triage summary.