E2e Testing skills

Agent Host E2E Tests

microsoft

Streamline testing for agent host functionality.

E2E Studio Tests

supabase

Run and debug Playwright tests for Supabase Studio.

Playwright Java

davila7

Automate E2E testing in Java with Playwright.

Senior QA Engineer

alirezarezvani

Automate testing and improve quality for React/Next.js apps.

Playwright Expert

jeffallan

Master E2E testing with Playwright for reliable browser automation.

Playwright E2E Testing

prowler-cloud

Streamline your Playwright end-to-end testing workflow.

Tuistory

cline

Drive and test terminal apps headlessly with ease.

QA Generate E2E Tests

bmad-code-org

Automate your end-to-end testing process with ease.

C

Cypress Automation

sickn33

Generate production-grade Cypress tests effortlessly.

E2E Testing Patterns

wshobson

Master end-to-end testing for reliable software delivery.

I

Initialize Playwright Project

alirezarezvani

Quickly set up a Playwright testing environment.

W

Windows Desktop E2E Testing

affaan-m

Automate end-to-end testing for Windows desktop applications.

Testing Agent

ruvnet

Comprehensive testing and quality assurance specialist.

E2E Test Review

metabase

Streamline your Cypress E2E spec file reviews.

C

Cypress E2E Test Generator

metabase

Automate Cypress tests for Metabase components with ease.

E2E Tests Studio

mastra-ai

Automate behavior validation for frontend changes.

E2E Testing Patterns

affaan-m

Build stable and maintainable end-to-end tests with Playwright.

When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new failure mode to test (crashes, drains, zombies, lag, failover); or when a new correctness property needs asserting during runs. Trigger terms: personhog gate, chaos scenario, test harness, leader path regression, handoff bug, eviction, writer lag, acked write.

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.