browser-test

Plan and execute parallel browser-based UI tests for web applications.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill browser-test-alexiolan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/browser-test
Command: npx skills add https://github.com/alexiolan/craft-skills --skill browser-test-alexiolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and execute browser-based UI testing at scale by coordinating multiple agents in parallel to shorten feedback loops and improve UI quality.

Core Features & Use Cases

  • Parallel test planning: derive test scenarios from built features and group them into batches for concurrent execution.
  • Test plan orchestration: generate and review test plans with agent allocations, supporting up to 4-5 parallel batches.
  • Automated execution prompts: dispatch browser-tester agents using the tester-prompt.md context and a ready test plan.
  • Use Case: validate a new login flow across desktop and mobile UIs by executing parallel test batches against http://localhost:3000.

Quick Start

Describe the feature to test and run a parallel browser test plan automatically.

Frequently Asked Questions about browser-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel browser UI tests for a web application feature?▼

Parallel browser UI tests are executed by deriving test scenarios from a built feature, grouping them into independent batches, and dispatching multiple tester agents concurrently against your app URL to shorten feedback loops.

Can I execute automated test plans against a localhost development server?▼

Yes, automated test plan orchestration targets a default app URL such as http://localhost:3000, dispatching browser-tester agents to validate UI flows against your local development server environment.

How does parallel test planning work for UI automation scenarios?▼

Parallel test planning works by deriving test scenarios from built features and grouping them into independent batches, supporting up to 4-5 parallel tester agent allocations for concurrent execution and faster feedback.

Do I need specific test plan files to dispatch multiple tester agents?▼

Yes, test plan orchestration relies on specs or plans located under the .claude/plans directory and uses tester-prompt.md for agent prompts to dispatch browser-tester agents with a ready test plan.

What is the best way to validate a new login flow across desktop and mobile UIs?▼

The best way is executing parallel test batches against your app URL, dispatching multiple browser-tester agents to validate the login flow across desktop and mobile UIs concurrently for improved UI quality.

Are there limitations to how many parallel test batches can run during orchestration?▼

Test plan orchestration supports up to 4-5 parallel batches, grouping independent test scenarios to dispatch multiple tester agents concurrently while maintaining execution stability.