ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
Best use case
ck:test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
Teams using ck:test should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:test Compares
| Feature / Agent | ck:test | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Testing & Quality Assurance Comprehensive testing framework covering code-level testing (unit, integration, e2e), UI/visual testing via browser automation, coverage analysis, and structured QA reporting. ## Default (No Arguments) If invoked with context (test scope), proceed with testing. If invoked WITHOUT arguments, use `AskUserQuestion` to present available test operations: | Operation | Description | |-----------|-------------| | `(default)` | Run unit/integration/e2e tests | | `ui` | Run UI tests on a website | Present as options via `AskUserQuestion` with header "Test Operation", question "What would you like to do?". ## Core Principle **NEVER IGNORE FAILING TESTS.** Fix root causes, not symptoms. No mocks/cheats/tricks to pass builds. ## When to Use - **After implementation**: Validate new features or bug fixes - **Coverage checks**: Ensure coverage meets project thresholds (80%+) - **UI verification**: Visual regression, responsive layout, accessibility - **Build validation**: Verify build process, dependencies, CI/CD compatibility - **Pre-commit/push**: Final quality gate ## Workflows ### 1. Code Testing (`references/test-execution-workflow.md`) Execute test suites, analyze results, generate coverage. Supports JS/TS (Jest/Vitest/Mocha), Python (pytest), Go, Rust, Flutter. Includes working process, quality standards, and tool commands. **Load when:** Running unit/integration/e2e tests, checking coverage, validating builds ### 2. UI Testing (`references/ui-testing-workflow.md`) Browser-based visual testing via `ck:chrome-devtools` skill. Screenshots, responsive checks, accessibility audits, form automation, console error collection. Includes auth injection for protected routes. **Load when:** Visual regression testing, UI bugs, responsive layout checks, accessibility audits ### 3. Report Format (`references/report-format.md`) Structured QA report template: test results overview, coverage metrics, failed tests, performance, build status, recommendations. **Load when:** Generating test summary reports ## Quick Reference ``` Code tests → test-execution-workflow.md npm test / pytest / go test / cargo test / flutter test Coverage: npm run test:coverage / pytest --cov UI tests → ui-testing-workflow.md Screenshots, responsive, a11y, forms, console errors Auth: inject-auth.js for protected routes Reports → report-format.md Structured QA summary with metrics & recommendations ``` ## Working Process 1. Identify testing scope from recent changes or requirements 2. Run typecheck/analyze commands to catch syntax errors first 3. Execute appropriate test suites 4. Analyze results — focus on failures 5. Generate coverage reports if applicable 6. For frontend: run UI tests via `ck:chrome-devtools` skill 7. Produce structured summary report ## Tools Integration - **Test runners**: Jest, Vitest, Mocha, pytest, go test, cargo test, flutter test - **Coverage**: Istanbul/c8/nyc, pytest-cov, go cover - **Browser**: `ck:chrome-devtools` skill for UI testing (screenshots, ARIA, console, network) - **Analysis**: `ck:ai-multimodal` skill for screenshot analysis - **Debugging**: `ck:debug` skill when tests reveal bugs requiring investigation - **Thinking**: `ck:sequential-thinking` skill for complex test failure analysis ## Quality Standards - All critical paths must have test coverage - Validate happy path AND error scenarios - Ensure test isolation — no interdependencies - Tests must be deterministic and reproducible - Clean up test data after execution - Never ignore failing tests to pass the build ## Report Output Use naming pattern from `## Naming` section injected by hooks. ## Team Mode When operating as teammate: 1. On start: check `TaskList`, claim assigned/next unblocked task via `TaskUpdate` 2. Read full task description via `TaskGet` before starting 3. Wait for blocked tasks (implementation) to complete before testing 4. Respect file ownership — only create/edit test files assigned 5. When done: `TaskUpdate(status: "completed")` then `SendMessage` results to lead
Related Skills
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.
ck:tanstack
Build with TanStack Start (full-stack React framework), TanStack Form (headless form management), and TanStack AI (AI streaming/chat). Use when creating TanStack projects, routes, server functions, forms, validation, or AI chat features.