browser-testing
Use when testing web applications, debugging browser console errors, automating form interactions, or verifying UI implementations. Load for localhost testing, authenticated app testing (Gmail, Notion), or recording demo GIFs. Requires Chrome extension 1.0.36+, Claude Code 2.0.73+, paid plan.
Best use case
browser-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when testing web applications, debugging browser console errors, automating form interactions, or verifying UI implementations. Load for localhost testing, authenticated app testing (Gmail, Notion), or recording demo GIFs. Requires Chrome extension 1.0.36+, Claude Code 2.0.73+, paid plan.
Teams using browser-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/browser-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How browser-testing Compares
| Feature / Agent | browser-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when testing web applications, debugging browser console errors, automating form interactions, or verifying UI implementations. Load for localhost testing, authenticated app testing (Gmail, Notion), or recording demo GIFs. Requires Chrome extension 1.0.36+, Claude Code 2.0.73+, paid plan.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Browser Testing Test and debug web applications via Chrome integration. ## Prerequisites | Requirement | Minimum | |-------------|---------| | Chrome extension | 1.0.36+ | | Claude Code CLI | 2.0.73+ | | Plan | Pro/Team/Enterprise | ## Instructions 1. Enable Chrome: `claude --chrome` or `/chrome` 2. Get tab context: `tabs_context_mcp` 3. Navigate: `navigate` to URL 4. Interact: `find`, `form_input`, `computer` 5. Verify: `read_console_messages`, `read_page` 6. Evidence: `computer(action="screenshot")` ## Quick Commands ```bash # Check for console errors scripts/check-console-errors.sh TAB_ID # Verify page loaded scripts/verify-page-load.sh TAB_ID URL # Run smoke test scripts/smoke-test.sh URL ``` ## MCP Tools | Tool | Purpose | |------|---------| | `tabs_context_mcp` | Get tab IDs (call first) | | `navigate` | Go to URL | | `computer` | Click, type, screenshot | | `find` | Find element by description | | `form_input` | Fill form fields | | `read_console_messages` | Debug with pattern filter | | `read_page` | Get DOM/accessibility tree | | `gif_creator` | Record interactions | ## References | File | Load When | |------|-----------| | references/patterns.md | Designing test scenarios | | references/examples.md | Need concrete examples |
Related Skills
bun-testing
Testing guidelines for Bun/TypeScript projects using bun:test framework. Use when writing tests, creating test files, debugging test failures, setting up mocks, or reviewing test code. Triggers on *.test.ts files, test-related questions, mocking patterns, and coverage discussions.
browser-fetch
Delegate browser automation to a lightweight subagent (Haiku) to reduce context consumption. Also provides web clipping (HTML→Markdown) via clipper.
Browser Automation Expert
浏览器自动化与网页测试专家。支持基于 MCP 工具（Puppeteer/Playwright）的实时交互，以及基于 Python 脚本的复杂自动化流实现。
backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
Appium Mobile Testing
Mobile app testing automation for iOS and Android with Appium
api-testing
REST and GraphQL API testing with Playwright. Use when testing APIs, mocking endpoints, validating responses, or integrating API tests with E2E flows.
API Testing Expert
API testing - Postman, REST clients, contract testing, mock servers
always-works-testing
Default testing standard for all implementation work - ensures code actually works through mandatory execution validation before confirming to user. Applies automatically whenever writing, modifying, debugging, or implementing any code (scripts, APIs, UI, configs, data operations, logic changes). This is the baseline expectation, not an optional extra - every implementation must be verified through actual execution, not assumed correct.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
dotnet-ui-testing-core
Tests UI across frameworks. Page objects, test selectors, async waits, accessibility.
browser-debugger
Systematically tests UI functionality, validates design fidelity with AI visual analysis, monitors console output, tracks network requests, and provides debugging reports using Chrome DevTools MCP. Use after implementing UI features, for design validation, when investigating console errors, for regression testing, or when user mentions testing, browser bugs, console errors, or UI verification.
accessibility-testing
Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.