Total 30,649 skills, Testing & QA has 1240 skills
Showing 12 of 1240 skills
Combinatorial testing with a greedy pairwise matrix generator. Covers all factor pairs in near-minimal test cases.
Snapshot test email templates using Verify to catch regressions. Validates rendered HTML output matches approved baseline. Works with MJML templates and any email renderer.
Write unit and integration tests for Akka.NET actors using modern Akka.Hosting.TestKit patterns. Covers dependency injection, TestProbes, persistence testing, and actor interaction verification. Includes guidance on when to use traditional TestKit.
Write integration tests using .NET Aspire's testing facilities with xUnit. Covers test fixtures, distributed application setup, endpoint discovery, and patterns for testing ASP.NET Core apps with real dependencies.
Write BDD test scenarios in Gherkin for a feature
TDD and testing skills for iOS/macOS apps. Covers characterization tests, TDD workflows, test contracts, snapshot tests, and test infrastructure. Use for test-driven development, adding tests to existing code, or building test infrastructure.
Execute, validate, and debug Midscene YAML automation files. Handles dry-run, execution, report analysis, and iterative debugging.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Run git-workspace-review first to understand which tests need updates. Use when updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation. Do not use when auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first.
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Use this skill at the BEGINNING of any detailed review for consistent structure. Use when starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs. Do not use when quick catchup without formal review - use catchup. DO NOT use when: diff-focused analysis - use diff-analysis.
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.