use-cases/qa-your-app-with-computer-use.md +77 −0 added
1---
2name: QA your app with Computer Use
3tagline: Click through real product flows and log what breaks.
4summary: Use Computer Use to exercise key flows, catch issues, and finish with a
5 bug report.
6bestFor:
7 - Teams validating real user flows before a release
8 - QA loops that should end with severity, repro steps, and a short triage
9 summary
10starterPrompt:
11 title: Run a Structured QA Pass
12 body: |-
13 @Computer Test my app in [environment].
14
15 Test these flows:
16 - [hero use case 1]
17 - [hero use case 2]
18 - [hero use case 3]
19
20 For every bug you find, include:
21 - repro steps
22 - expected result
23 - actual result
24 - severity
25
26 Keep going past non-blocking issues and end with a short triage summary.
27relatedLinks:
28 - label: Computer Use
29 url: /codex/app/computer-use
30 - label: Codex skills
31 url: /codex/skills
32---
33
34## Introduction
35
36Computer 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.
37
38The key is to tell Codex what environment to test, which flows matter most, and what kind of report you want back.
39
40## How to use
41
421. Install the [Computer Use plugin](https://developers.openai.com/codex/app/computer-use).
432. Tell Codex which app, build, or environment to test.
443. Name the flows or hero use cases you care about most.
454. Ask for a structured report so the output is easy to triage or hand off.
46
47You can keep this broad:
48
49- `@Computer Test my app. Find any major issues and give me a report.`
50
51Or make it more explicit:
52
53- `@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.`
54
55If you already maintain a test-plan file in the repo, attach it to the thread or point Codex at it so the QA pass follows your existing flows.
56
57## Practical tips
58
59### Be explicit about setup
60
61If 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.
62
63### Name the issue types you care about
64
65Call out whether you want Codex to focus on broken functionality, layout issues, confusing copy, visual regressions, or all of the above.
66
67### Decide whether to stop or continue
68
69If 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.
70
71## Good follow-ups
72
73After the QA pass, keep the same thread 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.
74
75## Suggested prompt
76
77**Run a Structured QA Pass**