Control Ui E2e
Control UI browser tests, visual reviews and recordings, interaction performance audits, and Run Inspector evidence.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Control Ui E2e when an AI agent needs a reusable SKILL.md workflow for this job: Control UI browser tests, visual reviews and recordings, interaction performance audits, and Run Inspector evidence.
When not to use it
Skip Control Ui E2e when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/control-ui-e2e # Save SKILL.md to ~/.claude/skills/control-ui-e2e/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/control-ui-e2e/SKILL.md. For a shared project, commit the folder at .claude/skills/control-ui-e2e/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Control Ui E2e skill for this task: Select proof. Use the existing browser E2E lane for routing, boot, Gateway. Confirm any required inputs or files before making changes.
What supports this recommendation?
72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Control UI E2E
## Workflow
1. **Select proof.** Use the existing browser E2E lane for routing, boot, Gateway handshake, and complete user flows; use browser/unit tests for isolated render logic. Read each branch below that matches the requested outcome. **Done:** every changed behavior has a named scenario and proof boundary. 2. **Prepare fixtures.** Reuse `ui/src/test-helpers/control-ui-e2e.ts` with synthetic Gateway data. Extend its typed scenario options for missing responses. Use the existing dependency installation; preserve installs used by other jobs. Real Gateway/provider credentials require explicit live-proof authorization. Follow [testing policy](../openclaw-testing/SKILL.md) for execution placement. **Done:** the target flow runs against the intended source or production build and each required fixture response is defined. 3. **Exercise behavior.** Install the mock before navigation. Act through visible controls and assert both the rendered outcome and relevant Gateway requests. Resolve unexpected behavior at the product or fixture owner before replaying. **Done:** each scenario reaches its asserted outcome, or has a retained failure identifying the unmet assertion. 4. **Deliver evidence.** Apply the artifact rules below and the selected branch's checks. Report verified results, failures, and untested states separately. **Done:** every claimed result has inspectable evidence; remaining gaps are named.
## UI Stress Test
For substantial layout/component changes or multi-state design feedback, read [visual proof](references/visual-proof.md#ui-stress-test) before building the stress-test gallery. Small copy/icon changes may use focused proof.
## Visual Proof Default
For appearance changes, screenshots, transient-state capture, or video, read [visual proof](references/visual-proof.md). Appearance changes require inspected before/after evidence; behavior assertions alone can suffice for nonvisual fixes.
## Interaction Performance Audits
For UI slowness, responsiveness audits, or automatic Chrome trace collection, read [interaction profiling](references/interaction-performance.md) before choosing the build, fixtures, and measurement boundaries.
## Run Inspector evidence
For run/execution/decision evidence, read [Run Inspector capture](references/run-inspector.md) before selecting a receipt.
## Artifacts
- Allocate with `createControlUiE2eArtifactDir(scope, parentDir?)`, once per attempt or standalone invocation. Pass the directory to capture helpers; keep distinct stage filenames and the report, screenshots, traces, and video together. - The helper owns parent selection. Preserve existing output controls, gates, viewport, and recording options; use its returned path in the final report. - Retain failed and successful attempts. Clean up only exact owned directories after review; never clear shared artifact parents or overwrite earlier proof. - Timeout diagnostics use fresh children of their existing diagnostic parent. Mantis retains every attempt. Real-Gateway, `chat-outbox-*`, and `chat-attachment-read-lifecycle` suites have separate owners: verify their retention behavior before claiming replay-safe capture.
## Running a focused test
Use the current scripts in `package.json` and [testing policy](../openclaw-testing/SKILL.md). For a worktree's focused browser test:
```bash node scripts/run-vitest.mjs run --config test/vitest/vitest.ui-e2e.config.ts --configLoader runner ui/src/e2e/chat-flow.messaging.e2e.test.ts ```
Intended uses
- Select proof. Use the existing browser E2E lane for routing, boot, Gateway
- Prepare fixtures. Reuse ui/src/test-helpers/control-ui-e2e.ts with synthetic
- Exercise behavior. Install the mock before navigation. Act through visible
- Deliver evidence. Apply the artifact rules below and the selected branch's
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.