Results for “interaction-testing”

Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.

Automates browser testing and interaction with Playwright, including form filling, screenshots, responsive checks, and login flows, with automatic dev server detection.

Automates browser interactions and testing with Playwright, including form filling, screenshots, responsive checks, and login flows, with automatic dev server detection.

Use this when the team needs detailed interaction behavior for user inputs, transitions, feedback, validation, confirmations, or stateful UI behavior that should be implementation-ready rather than purely visual.

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.

Provides a Flutter testing strategy covering unit, widget, integration, and BLoC tests with code examples, dependencies, and coverage commands.

Guides writing behavior-focused React component and hook tests with React Testing Library, Vitest/Jest, MSW network mocking, and axe accessibility assertions, including when to use component vs end-to-end tests.

Runs an interactive QA session, clarifying user-reported problems, exploring the codebase for context, and filing durable, user-focused GitHub issues.

Design interaction flows, states, and microinteractions for usability and feedback clarity. Use when: (1) defining flows, (2) state/error handling, (3) reducing cognitive load. NOT for: final code implementation.

Three.js interaction - raycasting, controls, mouse/touch input, object selection. Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences.

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.

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

Use when writing or modifying tests for Ink (terminal UI) components.

Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs.

Prevents AI-introduced regressions with sandbox-mode API testing, automated bug-check workflows, and patterns that catch blind spots where the same model writes and reviews code.

Collects publicly available information about a target organization to identify attack surfaces, social engineering targets, technology stacks, and credential exposures for authorized security testing.

A/B and multivariate testing methodology. Design experiments, calculate sample sizes, determine statistical significance, avoid common pitfalls, and interpret results. Platform-agnostic framework applicable to landing pages, emails, ads, pricing, and product features. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, or conversion experiments.

Internal architecture and change-impact review assistant for this repository.

Comprehensive web application testing patterns with Playwright selectors, wait strategies, and best practices

Performs load testing with Locust, Python-based distributed testing, and real-time web UI.

Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs.

Transforms A/B test and product experiment data into actionable readouts with hypothesis, metrics, interpretation, and decision.

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.

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.

Create systematic QA checklists to verify that design implementations match specifications across visual accuracy, layout, interaction, content, accessibility, and cross-platform categories.

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

Route browser, UI QA, smoke testing, click-path auditing, Webwright, and desktop app automation prompts. Use when prompts mention browser QA, Playwright, smoke tests, app/browser interaction, click paths, screenshots, Webwright, or Windows desktop E2E.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Use for writing, reviewing, debugging, or testing Python Streamlit apps, especially rerun behavior, widget identity and callbacks, session_state, cache_data/cache_resource, forms, fragments, containers, multipage navigation, uploads/downloads, and Streamlit-hosted chart/table interaction. Do not use for standalone Plotly/Altair figure design, generic backend services, Dash apps, or deployment configuration without app code.