Results for “interaction-testing”

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, or extract information from web pages.

Write behavior-focused React component tests with React Testing Library, Vitest/Jest, MSW for network mocking, and accessibility assertions using axe, while deciding when to use component tests versus Playwright/Cypress end-to-end tests.

Test React components with RTL and Jest/Vitest. Use when writing React component tests with React Testing Library, Jest, or Vitest.

React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.

Runs adversarial UI tests in a real browser, covering functional, accessibility, responsive, and UX checks, with diff-driven, exploratory, and parallel workflows.

Run multiple AI agents against a product, SDK, or docs site to score setup friction, speed, efficiency, error recovery, and doc quality from a minimal prompt.

`analysis-agent`/`task-agent`/`review-agent`: use for component, route, browser, accessibility, and API-backed UI-state tests; skip backend, portfolio, and release-verdict work.

Use `analysis-agent` to map user-flow, interaction-state, accessibility, content, and recovery impact when experience behavior changes. Skip backend-only work with no experience effect and question-only requests.

Use when writing or modifying tests for React hooks.

Use `task-agent` for bounded frontend component or browser changes involving interaction, accessibility, API failures, security, or regression proof. Skip backend-only work and design exploration without implementation.

Automates browser interactions — navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, and running assertions — using a native Rust CLI.

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, or extract information from web pages.

Generates a Playwright test from a user-provided scenario by recording browser interactions via Playwright MCP, then saves and runs the test until it passes.

Automate web browser interactions using natural language via CLI commands. Supports local and remote Browserbase sessions with CAPTCHA solving, residential proxies, and session persistence.

Secure and powerful Playwright browser automation for testing websites, checking deploys, taking screenshots, filling forms, validating login flows, responsive QA, deploy QA, accessibility smoke checks, and browser-based verification. Use when Nick asks to test a page, verify a deployment, automate browser interactions, capture screenshots, inspect console errors, check mobile/desktop rendering, or run real Chromium-based browser checks.