Total 43,644 skills, Testing & QA has 1613 skills
Showing 12 of 1613 skills
Design accessibility testing plans and test cases covering WCAG 2.1 standards, screen readers, and keyboard navigation. Default output is Markdown, with support for requesting Excel/CSV/JSON formats. Use for accessibility testing.
Generate professional test reports, including executive summaries, metrics, defect analysis, and risk assessments. Support daily reports, weekly reports, release reports, etc. The default output is Markdown, and Excel/CSV/JSON/PDF formats are available upon request. Use for test reporting.
Design API test plans and cases for REST/GraphQL/gRPC interfaces. Default output Markdown; can request Excel, CSV, or JSON. Use for API testing.
Utilize AI to assist in testing activities, including test data generation, defect root cause analysis, test prioritization, and intelligent test recommendation. The default output format is Markdown, and you can request Excel/CSV/JSON formats instead. This skill applies to AI-assisted testing scenarios.
Design manual testing and exploratory testing plans, including test charters, heuristic methods, and session records. Default output is Markdown, Excel/CSV/JSON is available upon request. Use for manual testing.
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.
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`.
WCAG 2.2 AA compliance expert specializing in audits, automated testing, screen reader validation, and remediation.
Use when writing Gherkin feature files, using Scenario Outline with Examples, applying tags for test organization, and leveraging Background sections for shared setup.
Use when writing or reviewing Java unit tests. Enforces Mockito/JUnit 5 best practices - strict stubbing, no lenient mode, specific matchers, complete flow stubbing, Arrange-Act-Assert structure, and clear test naming.
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 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".