From yellow-browser-test
Testing conventions and configuration reference. Use when agents or commands need config schema, severity classification, report templates, or credential rules for browser testing.
npx claudepluginhub kinginyellows/yellow-plugins --plugin yellow-browser-testThis skill uses the workspace's default tool permissions.
Reference conventions for the yellow-browser-test plugin's testing workflow.
Automates E2E testing and browser interactions with qa-use CLI. Create sessions, navigate pages, snapshot DOM for element refs, perform clicks/fills, and debug test failures.
Drives Chrome browser sessions against running web apps to detect bugs, UX issues, accessibility violations, performance problems, and copy errors, outputting structured JSON findings for QA passes, smoke tests, or audits.
Runs ScoutQA CLI for AI-powered exploratory testing of web apps, including smoke tests, accessibility audits, login flows, and e-commerce validation. Proactive after feature implementation.
Share bugs, ideas, or general feedback.
Reference conventions for the yellow-browser-test plugin's testing workflow. Defines the config schema, report format, severity levels, and safety rules.
Use when yellow-browser-test commands or agents need the config schema, severity classification, or credential handling rules.
This skill is not user-invokable. It provides shared context for the yellow-browser-test plugin.
Config is stored at .claude/yellow-browser-test.local.md as YAML frontmatter +
markdown notes.
---
schema: 1
generated: '2026-02-13T10:30:00Z'
devServer:
command: 'npm run dev'
port: 3000
baseURL: 'http://localhost:3000'
readyTimeout: 60
readyPath: '/'
auth:
type: 'email-password'
loginPath: '/login'
credentials:
email: '$BROWSER_TEST_EMAIL'
password: '$BROWSER_TEST_PASSWORD'
formFields:
email: 'email'
password: 'password'
routes:
- path: '/dashboard'
name: 'Dashboard'
auth: true
---
Required fields: schema, devServer.command, devServer.baseURL
| Severity | Criteria | Example |
|---|---|---|
| critical | App crashes, data loss, security hole | Unhandled exception on form submit |
| major | Feature broken, console error, blank section | Settings page renders empty |
| minor | Slow load, UI glitch, non-blocking error | Button misaligned, 5s load time |
| cosmetic | Visual imperfection, typo | Font inconsistency, extra whitespace |
$BROWSER_TEST_EMAIL).claude/browser-test-auth.json must be gitignored.claude/browser-test-server.pid must be gitignoredBROWSER_TEST_* prefix for all test credentials
(e.g., BROWSER_TEST_EMAIL, BROWSER_TEST_PASSWORD)***.claude/browser-test-auth.json and re-run setup to refresh auth stateDuring autonomous exploration, the test-runner agent MUST:
Reports are written to test-reports/YYYY-MM-DD-HH-MM.md. See test-reporter
agent for full template and GitHub issue creation flow.
Security: ALWAYS use AskUserQuestion before creating GitHub issues. Never auto-create. Warn that screenshots may contain sensitive data.