browser-load-test

Run Playwright load scenarios against the Frood dashboard to determine concurrent agent limits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SalesTeamToolbox/frood --skill browser-load-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-load-test
Source: https://github.com/SalesTeamToolbox/frood/tree/main/skills/builtins/browser-load-test
Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill browser-load-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, httpx.

What problem does it solve?

This Skill helps you determine the true concurrent agent capacity of the Frood dashboard so you can avoid surprises under load and tune dispatch, routing, and rate limits.

Core Features & Use Cases

  • Playwright-driven load testing: Executes Playwright browser flows against the dashboard UI to simulate realistic user interaction.
  • API-and-queue saturation detection: Submits tasks through the browser UI and API, polling status until scaling stops and capturing the saturation point.
  • Evidence capture for post-analysis: Saves screenshots and a time-series metrics JSON file to understand what happened at warmup, peak stress, and cooldown.

Quick Start

Run the monitor in one terminal and start the default load test in another by running: python load_test.py.

Frequently Asked Questions about browser-load-test

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

FAQPage Schema
How do I find real concurrent agent limits for a dashboard?

Playwright browser load testing finds real concurrent agent limits by simulating realistic user interaction through the dashboard UI and API. It applies to capacity planning, scaling validation, and debugging dispatch behavior for complex multi-agent workloads.

How do I run a load test to detect dashboard capacity saturation?

Run the monitor in one terminal and execute the load test script in another to submit tasks via UI and API. Scripted phases of warmup, teams, stress, and cooldown poll status until saturation stops, outputting screenshots and time-series metrics JSON.

What output artifacts does a Playwright load test generate for post-analysis?

Playwright load testing generates screenshots and a time-series metrics JSON file for post-analysis. These artifacts capture evidence of dashboard behavior during warmup, peak stress, and cooldown phases to understand scaling limits and dispatch routing.

Do I need Playwright and httpx to perform browser-based load testing?

Yes, you need Playwright and httpx dependencies to perform browser-based load testing. Playwright drives browser UI flows simulating realistic user interaction, while httpx handles API task submissions required to saturate dashboard queues.

Can I use Playwright load testing for debugging multi-agent dispatch behavior?

Yes, you can use Playwright load testing for debugging multi-agent dispatch behavior. It applies to debugging dispatch behavior for complex multi-agent workloads by submitting tasks and capturing metrics time-series JSON evidence during stress phases.

Why does dashboard dispatch behavior break under high concurrency?

Dashboard dispatch behavior breaks under high concurrency when real concurrent agent limits are exceeded. Load testing identifies this saturation point by polling task status until scaling stops, helping tune dispatch routing and rate limits to prevent failures.