qa-unit-test-creation
Vitest unit test creation patterns. Provides patterns for AAA structure, mocking, fixtures, and test data factories. Use when creating unit tests for components, services, utilities, or stores.
Découvrez les skills data ai testing, comparez leurs dépôts et consultez leurs instructions.
Vitest unit test creation patterns. Provides patterns for AAA structure, mocking, fixtures, and test data factories. Use when creating unit tests for components, services, utilities, or stores.
Debug by reproducing, minimizing, writing regression tests, fixing, and documenting.
Automates mock test creation for C++ projects using Google Mock (GMock) framework with consistent software testing patterns. Use when creating tests with mocked dependencies, interface mocking, behavior verific...
Implement a feature end-to-end based on its spec/features file.
Use this skill when validating built features through conversational testing, running UAT, user acceptance testing, checking if features work, or verifying implementation. Triggers include "verify work", "test...
E2E test creation for Developer - write tests using Playwright API for feature validation
Public package tester for GitHub repositories. Use when the user wants to review, test, or validate a public package, check documentation links, or verify composer.json quality.
Player input validation testing patterns for WASD, mouse, and touch controls
E2E gameplay testing patterns using Playwright API. Tests continuous movement, mouse control, and complete gameplay loops. Use when validating game controls, combat mechanics, and player interactions.
Testing patterns for Prowler SDK (Python). Trigger: When writing tests for the Prowler SDK (checks/services/providers), including provider-specific mocking rules (moto for AWS only).
Agent Acceptance Testing - hypothesis-driven PR verification protocol
Automates fuzz test creation for C++ projects using consistent software testing patterns. Use when creating fuzz tests, mutation testing, or when the user mentions fuzzing, libFuzzer, or AFL.
Shared helper patterns for Playwright MCP validation agents. Reuses Page Object patterns from E2E tests.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage using Google Test and CMake/CTest.
Analyzes xcresult bundles to provide insights on test failures, slow tests, and potentially flaky tests. Use when user asks about test results, test failures, slow tests, or test coverage.
Implements Test-Driven Development for this project—unit tests, integration tests with testcontainers, mocks, and regression tests. Use when writing or fixing tests, reproducing bugs with tests, or improving co...
PHP Laravel test creation specialist. Use when the user wants to create, write, or generate tests for PHP/Laravel code. Follows project conventions and ensures 100% coverage.
Test coverage check and creation workflow. Ensures tests exist for all features. Creates unit and E2E tests when missing following acceptance criteria. Use during validation before code review.
Asset loading performance validation using Playwright. Use when validating FBX model loading performance and memory usage, testing asset loading across different environments, ensuring proper error handling for...
Use when generating functional test scenarios from workflow decompositions. Use when developers need test cases, when validating workflow completeness, or when preparing acceptance criteria for AI-assisted proc...
Use when specifying testable acceptance criteria for user stories. Use after user story drafted. Produces Given-When-Then scenarios, edge case coverage, and validation approach.
Generates unit tests, integration tests, and E2E tests using Vitest and Playwright. USE WHEN user says 'write tests', 'add tests', 'test this', OR wants testing coverage.
Add or improve tests based on a feature spec's acceptance criteria.
Create a feature spec under spec/features/ (and ADR if needed).
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.