3 tagged browserless, measured the same way as everything else here.
Agent
Use this agent to diagnose E2E test failures, analyze flaky tests, investigate network errors, and provide stability insights. Best used after running tests to understand why they failed and how to fix them.
Agent
Use this agent to create new E2E tests by exploring the application UI, analyzing source code, and designing test actions. Best used when you need to write tests for a new feature, page, or user flow.
Agent
Use this agent to improve existing E2E tests — refactor verbose evaluate actions into built-in alternatives, extract duplicated sequences into modules, replace brittle selectors, add missing waits/retries for flaky tests, and eliminate hardcoded delays. Best used when tests work but need cleanup.