UI Test
AI-powered adversarial UI testing via the browse CLI.
Install
npx skills add browserbase/skills --skill ui-test -g -a claude-code -y- Repository
- browserbase/skills3.7k
- Category
- Design
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).
UI Test, Agentic UI Testing Skill
Test UI changes in a real browser. Your job is to try to break things, not confirm they work.
Three workflows:
- Diff-driven, analyze a git diff, test only what changed
- Exploratory, navigate the app, find bugs the developer didn't think about
- Parallel, fan out independent test groups across multiple Browserbase browsers
How Testing Works
The main agent coordinates, it plans test strategy, delegates to sub-agents, and merges results. Sub-agents do the actual browser testing.
Planning: multiple angles, then execute once
You MUST complete all three planning rounds yourself and output them before launching any sub-agents. Planning happens in your own response, it is NOT delegated to sub-agents. Do not skip ahead to execution.
Round 1, Functional: What are the core user flows? What should work? Write out each test as: action → expected result.
Round 2, Adversarial: Re-read Round 1. What did you miss? Think about: different user types/roles, error paths, empty states, race conditions, edge inputs (empty, huge, special chars, rapid clicks).
Round 3, Coverage gaps: Re-read Rounds 1, 2. What about: accessibility (axe-core, keyboard-only), mobile viewports, console errors, visual consistency with the rest of the app?
Deduplicate: Merge all three rounds into one numbered list of tests. Remove overlaps. Assign each test to a group (e.g. Group A, Group B).
Then execute once, launch one sub-agent per group. Each sub-agent receives its specific list of tests to run, nothing more. Sub-agents do not explore or plan, they execute assigned tests and report results.
Output the three rounds, the merged plan, and the group assignments in your response before calling any Agent tool.
