test

name	test
description	Test planning, generation, and execution -- unit, integration, and end-to-end testing workflows
layer	hub
category	workflow
triggers	["/test","write tests","test this","add test coverage","run the tests","check if tests pass"]
inputs	[{"target":"Code, feature, or file(s) to test"},{"testType":"unit | integration | e2e | all (optional, defaults to appropriate type)"},{"framework":"Test framework to use (optional, auto-detected from project config)"}]
outputs	[{"testPlan":"Strategy document listing what to test and why"},{"testFiles":"Generated test file(s) with complete test cases"},{"testResults":"Output from running the tests"},{"coverageReport":"Coverage summary for the tested area (if available)"}]
linksTo	["scout","debug","fix","code-review"]
linkedFrom	["fix","refactor","optimize","cook","team","ship"]
preferredNextSkills	["code-review","fix"]
fallbackSkills	["debug","scout"]
riskLevel	low
memoryReadPolicy	selective
memoryWritePolicy	selective
sideEffects	["Creates or modifies test files","Runs test commands","May install test dependencies"]

Test Skill

Purpose

Plan, generate, and execute tests that verify code correctness, prevent regressions, and document expected behavior. This skill covers the full testing lifecycle from strategy through execution.

Tests are not bureaucracy. Tests are executable documentation that proves your code works.

Workflow

Mode 1: Test Planning

Use when you need to decide WHAT to test before writing tests.

1. Identify the testing target -- What code/feature needs tests?
2. Read the target code -- Understand what it does, its inputs, outputs, and edge cases.
3. Detect existing test infrastructure
   • What test framework is in use? (Jest, Vitest, pytest, Go testing, etc.)
   • Where do tests live? (co-located, separate tests/ directory, __tests__ folders)
   • What testing utilities exist? (test helpers, factories, mocks, fixtures)
   • What is the test runner command?
4. Categorize test needs:
   • Unit tests: Individual functions/methods in isolation
   • Integration tests: Multiple components working together
   • E2E tests: Full user flows through the system
5. Produce the test plan:

# Test Plan: [Target]

## Target
[What is being tested]

## Test Infrastructure
- **Framework**: [name + version]
- **Runner command**: [command]
- **Test location**: [where tests should go]

## Unit Tests
| Test | Input | Expected Output | Edge Case? |
|------|-------|----------------|------------|
| [function] handles valid input | [input] | [output] | No |
| [function] handles empty input | [] | [] or error | Yes |
| [function] handles null | null | throws TypeError | Yes |

## Integration Tests
| Test | Components | Scenario |
|------|-----------|----------|
| [feature] happy path | A + B + C | [description] |
| [feature] error propagation | A + B | [description] |

## Edge Cases to Cover
- [edge case 1]
- [edge case 2]


 [thing]: [reason -- e.g., "covered by upstream tests"]