Unit Testing
5220 skills in Testing & Security > Unit Testing
flutter-test
Run Flutter tests and analyze results. Use when implementing game logic, fixing bugs, or validating changes. Triggers on "run tests", "test this", "verify", "check if it works".
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
test-skill
A test skill for validation
docs-test-review
ドキュメント・テスト品質レビュー - コメント品質、API仕様、テストの意味、カバレッジを統合評価
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior and production pollution
testing
Patterns for testing pure functions using Deno's test framework. Covers unit tests, property-based testing, test organization, and assertion patterns. Use when writing tests. Includes script for generating test boilerplate.
backend-developer
Skill for PHP/Laravel backend development following project conventions. Use when creating or editing PHP code, models, services, controllers, tests, or any backend logic. Loads all backend rules from .claude/rules/backend/ and .claude/rules/dataclasses/.
error-memory
Use when: making a mistake, breaking build/tests, realizing wrong approach, misunderstanding requirements, using wrong patterns, forgetting conventions, receiving correction from user, unexpected behavior, or any error situation
n8n-preflight-agent
Validates n8n workflow JSON files, tests APIs with real credentials, auto-fixes common issues, and learns new problems. Use when you need to CHECK, VALIDATE, FIX, TEST, PREFLIGHT, or REPAIR n8n workflow JSON files before importing them.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup. Presents exactly 4 options: merge locally, create PR, keep as-is, or discard. Do NOT use when tests are failing or work is incomplete - fix issues first before finishing the branch.
tdd-playwright
Playwright 기반 TDD 개발을 지원합니다. 테스트 작성, 실행, 디버깅을 자동화하고 테스트가 통과할 때까지 반복 개발합니다. 사용자가 "TDD로 개발", "Playwright 테스트 작성", "테스트 통과시켜"와 같은 요청을 할 때 사용합니다.
ci-cd-pipelines
GitLab CI/CD pipeline patterns including testing stages, Docker builds, caching strategies, secrets management, deployment patterns (blue-green, canary, rolling), and rollback procedures. Use when creating .gitlab-ci.yml, optimizing CI performance, setting up deployment pipelines, or troubleshooting CI failures.
rxjs-patterns-for-angular
Implement RxJS patterns for reactive programming in Angular. Use this skill when working with Observables, operators, subscriptions, async data flows, and error handling. Covers common patterns like combineLatest, switchMap, debounceTime, catchError, retry logic, and integration with Angular Signals using toSignal() and toObservable(). Ensures proper subscription cleanup with takeUntilDestroyed().
coderabbit-request
Use after completing file changes - strongest for source code (AST-aware linting, security, tests), lighter support for markdown/config. Dispatches CodeRabbit reviewer subagent. ALWAYS request review before considering work complete.
ci-optimization-specialist
Optimizes GitHub Actions CI/CD workflows through test sharding, intelligent caching, and workflow parallelization. Use when CI execution time exceeds limits, costs are too high, or workflows need parallelization.
acceptance-criteria-generator
Creates testable acceptance criteria in Given/When/Then format for user stories
deploy
Execute the complete TestFlight deployment workflow for this Flutter iOS app. Use when the user asks to deploy, release, publish, or upload the app to TestFlight, or says things like "deploy to testflight", "release a new build", "push to beta testers", or "upload to app store connect".
python-test-strategy
Python unit testing patterns for pytest, including test file structure, fixtures, mocks, and coverage strategy. Use when asked to write tests (unit/integration) for any Python module, function, class, or method.
emit
Use when working on the Miden compiler (`cargo miden`, `cargo-miden`) and its integration test suite, debugging compiler issues or failing tests, or implementing compiler changes and you need to inspect intermediate artifacts. Covers `MIDENC_EMIT` (the environment-variable equivalent of `--emit`) for emitting WAT/HIR/MASM (and related outputs), plus `MIDENC_EMIT_MACRO_EXPAND` for dumping macro-expanded Rust via `cargo expand` for integration-test fixtures.
testing-skills-with-subagents
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes