Total 30,584 skills, Testing & QA has 1235 skills
Showing 12 of 1235 skills
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".
Testing principles, strategies, and patterns. Covers the testing pyramid, test design, TDD, test doubles, and common testing antipatterns. Stack-agnostic.
Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions. Use when testing game logic, verifying state changes, or ensuring system correctness.
Test-Driven Development workflow enforcement with RED-GREEN-REFACTOR cycle. Use when implementing features test-first or improving test coverage.
Use BEFORE brainstorming — when the user wants to capture WHAT a feature should do as Gherkin scenarios. Trigger when the user says "I need to build X", "let's spec this out", "what should this feature do?", or wants to formally capture a new edge case or bug as a BDD scenario.
Use when the user wants to validate that implemented code matches its specifications, generate integration tests from feature files, or check if code still satisfies existing scenarios. Trigger after implementation completes a feature. Also use when the user asks "does the code do what we specified?" or "generate tests from the feature files".
Configure specific Sentry features beyond basic SDK setup. Use when asked to monitor AI/LLM calls, set up OpenTelemetry pipelines, or create alerts and notifications.
Use when writing Gherkin feature files, using Scenario Outline with Examples, applying tags for test organization, and leveraging Background sections for shared setup.
WCAG 2.2 AA compliance expert specializing in audits, automated testing, screen reader validation, and remediation.
Use when you need to create defect reports that can be directly pasted into external defect systems (without saving bug files in the Spec Pack) during the verification phase of the Spec Pack, and write the defect references back to `{FEATURE_DIR}/verification/report-*.md`.
Guides release testing from T-14 planning through Go/No-Go, deployment, and post-release. Covers functional, regression, performance, security, accessibility. Use when planning or executing release testing.