testing▌

Comprehensive test case generation from PRD documents and user requirements with full coverage mapping. \n \n Transforms product requirements into structured, executable test cases organized by category: functional, edge case, error handling, and state transition scenarios \n Generates requirement-driven test cases with unique IDs, priority levels, preconditions, step-by-step actions, and measurable expected results \n Includes traceability matrix linking each requirement to corresponding test c

Multi-agent pipeline that generates compilable, passing unit tests across eight programming languages. \n \n Orchestrates a Research → Plan → Implement workflow: researcher analyzes the codebase, planner creates phased test strategy, implementer writes and validates tests across phases \n Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more; auto-detects language, testing framework, build commands, and project structure \n Includes builder, tester, fixer, and linter subagents th

Browser automation with 40+ commands for navigation, interaction, form filling, and web testing. \n \n Supports multiple browsers (Chrome, Firefox, WebKit, Edge) with persistent profiles, extensions, and custom configurations \n Core interactions include clicking, typing, dragging, selecting, uploading files, and handling dialogs across page elements \n Storage management for cookies, localStorage, and sessionStorage; network request mocking and routing for testing \n DevTools integration with c

Persona: You are a Go engineer who treats tests as executable specifications. You write tests to constrain behavior, not to hit coverage targets.

This skill provides expert guide for testing Spring Boot 4 applications with modern patterns and best practices.

Accessibility testing ensures web applications are usable by people with disabilities, including those using screen readers, keyboard navigation, or other assistive technologies. It validates compliance with WCAG (Web Content Accessibility Guidelines) and identifies barriers to accessibility.

Generate Playwright tests from scenarios using interactive browser exploration and validation. \n \n Guides you through step-by-step test creation: scenario review, browser exploration, element inspection, interaction validation, and final test generation \n Integrates with Playwright MCP tools to inspect page elements, capture selectors, and validate interactions before writing test code \n Generates TypeScript tests using @playwright/test framework and automatically saves them to the tests dir

44 Vitest best practices rules organized by priority, covering async patterns, test setup, mocking, performance, snapshots, and assertions. \n \n Async patterns and test isolation are marked CRITICAL; covers awaiting assertions, returning promises, fake timers, and proper cleanup between tests \n Mocking rules address vi.mock hoisting, spyOn vs mock selection, implementation patterns, and type safety \n Performance optimization includes pool selection, test isolation toggling, happy-dom preferen

Conduct effective usability testing using frameworks from 11 product leaders. \n \n Choose the right test fidelity: fake doors and Wizard of Oz tests for concept validation, prototypes for design feedback, production testing for optimization \n Small sample sizes (10 random users) reveal core friction points; direct observation of user behavior uncovers needs that surveys miss \n Test multiple design options simultaneously to measure relative performance, not single designs in isolation \n Bring

End-to-end testing focused on real user behavior, minimal mocking, and avoiding component unit tests. \n \n Prioritizes E2E tests over unit tests; reserves unit tests for pure functions only \n Emphasizes accessible selectors (role-based, label-based) over CSS selectors and test IDs in E2E tests \n Recommends writing E2E tests instead of heavily mocked unit tests; suggests 3+ mocks as a signal to switch approaches \n Includes rules for test structure, selector strategy, and when to apply each te