# 11 Browser QA

> Run post-review browser QA and produce short named videos for a locked happy path and sourced browser edge cases. Use when the user wants concise reviewer evidence for a web journey. Not for API, CLI, automated tests, diff review, or application fixes.

- Skill: `ai-driven-dev/11-browser-qa` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add ai-driven-dev/11-browser-qa`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ai-driven-dev/11-browser-qa/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: ai-driven-dev (https://skillmd.com/u/ai-driven-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ai-driven-dev/11-browser-qa

---


# Browser QA

```mermaid
flowchart LR
  prerequisites["prerequisites"] --> scope["load-scope"] --> prepare["prepare-run"] --> run["run-scenarios"]
```

## Actions

Read only the next action's file before running it.

| #   | Action          | Does                                                       |
| --- | --------------- | ---------------------------------------------------------- |
| 00  | `prerequisites` | Verify the browser runner and media dependencies            |
| 01  | `load-scope`    | Lock one happy path and a bounded set of sourced edge cases |
| 02  | `prepare-run`   | Resolve the shortest deterministic path to executable runs |
| 03  | `run-scenarios` | Record, normalize, verify, reset, and report every scenario |

## Transversal rules

- Run against a reviewed change and never patch the application.
- Never spawn agents. Batch independent reads and tool checks, but keep state-changing browser work sequential.
- Do not narrate action transitions, searches, fixtures, selectors, or successful checks. Report only a blocker, a required decision, or the final verdict and paths.