Unit Testing

Comprehensive BDD testing with Cucumber and Gherkin syntax. Use when writing feature files (.feature), step definitions, hooks, or implementing Behaviour-Driven Development. Covers Gherkin keywords (Feature, Scenario, Given/When/Then, Background, Scenario Outline, Rule), step definition patterns for Ruby/JavaScript/Java/Python, hooks (Before/After/BeforeAll/AfterAll), tags, data tables, doc strings, and best practices. Triggers on cucumber, gherkin, BDD, feature files, step definitions, acceptance testing, executable specifications.

Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.

This skill should be used when the user asks to "write tests", "add unit tests", "create test cases", "test this function", "add test coverage", or discusses testing strategies and test implementation.

Probability, distributions, hypothesis testing, and statistical inference. Use for A/B testing, experimental design, or statistical validation.

Complete TDD workflow for creating comprehensive failing test suites across all architectural layers (entities, use cases, services, APIs, E2E) using Vitest, Playwright, and Testing Library. Mandatory Context7 consultation for latest testing patterns.

Update ClaudeKit Engineer projects to the latest version. Capabilities include update single projects (safe mode with test branches), batch update multiple projects, find all ClaudeKit projects in home directory, verify updates with automated checks, preserve user settings and code, create timestamped backups, handle git workflows (branch, commit, merge), and rollback if needed. Use when user wants to update ClaudeKit framework, upgrade to latest version, apply new features/skills/commands, or maintain multiple ClaudeKit projects.

Эксперт Detox тестирования. Используй для React Native E2E tests и mobile automation.

Use when investigating test suite issues, reducing CI/CD time, identifying brittle tests, finding test duplication, or analyzing test maintenance burden - reveals test code quality problems through git history analysis

Testing workflow for quality assurance. Use after implementation to run tests, check coverage, and validate critical paths.

Test-Driven Development with Arcanean philosophy - write tests first, fail intentionally, implement minimally, refactor with confidence. Embodies the Arcanean principle that constraint liberates creativity.

Quick reference for Smithery and Cloudflare deployment operations. Use for deploying Canvas MCP server, managing workers on ariff.dev, and testing OAuth endpoints.

Browser automation with Playwright for Python. Recommended for visual testing. (project)

Complete Test-Driven Development workflow coordinating RED → GREEN → REFACTOR → COMMIT cycle with requirement traceability. Use this when implementing a requirement (REQ-*) or adding new functionality.

Deep code review with web research to verify against latest ecosystem. Use when user says 'double check against latest', 'verify versions', 'check security', 'review against docs', or needs deep analysis beyond automatic quality hook.

Integration Test E2E 테스트, TestRestTemplate 필수, Test Fixtures 재사용.MockMvc 금지, @Sql 어노테이션 테스트 데이터 설정.Gradle testFixtures 플러그인 활용, ArchUnit 의존성 검증.

Expert guidance for testing and validating GitHub Actions workflows before deployment - catches cache errors, path issues, monorepo dependencies, and service container problems that local testing misses

Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when the user asks to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift/checkpoints.

Automatically builds and tests code changes. Use whenever code is modified, tests fail, before creating pull requests, or when verifying code quality.

Background job manager for long-running commands. Triggers on: "run in background", "takes a while", "long running", builds >30s, test suites, deployments, dev servers, anything that should survive session disconnect.

This skill should be used when the user asks to "create a Next.js app", "build a page", "add routing", "implement server components", "add caching", "create API routes", "use server actions", "add metadata", "set up layouts", or discusses Next.js architecture, App Router, data fetching, or rendering strategies. Always use the latest Next.js version and modern patterns.