lmiranda
2e65b60725
Major refactoring of projman plugin architecture: Skills Extraction (17 new files): - Extracted reusable knowledge from commands and agents into skills/ - branch-security, dependency-management, git-workflow, input-detection - issue-conventions, lessons-learned, mcp-tools-reference, planning-workflow - progress-tracking, repo-validation, review-checklist, runaway-detection - setup-workflows, sprint-approval, task-sizing, test-standards, wiki-conventions Command Consolidation (17 → 12 commands): - /setup: consolidates initial-setup, project-init, project-sync (--full/--quick/--sync) - /debug: consolidates debug-report, debug-review (report/review modes) - /test: consolidates test-check, test-gen (run/gen modes) - /sprint-status: absorbs sprint-diagram via --diagram flag Architecture Cleanup: - Remove plugin-level mcp-servers/ symlinks (6 plugins) - Remove plugin README.md files (12 files, ~2000 lines) - Update all documentation to reflect new command structure - Fix documentation drift in CONFIGURATION.md, COMMANDS-CHEATSHEET.md Commands are now thin dispatchers (~20-50 lines) that reference skills. Agents reference skills for domain knowledge instead of inline content. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.9 KiB
description
| description |
|---|
| Run tests with coverage or generate tests for specified code |
Test
Skills Required
- skills/test-standards.md
Purpose
Unified testing command for running tests and generating new tests.
Invocation
/test # Default: run tests
/test run # Run tests, check coverage
/test run --coverage # Run with coverage report
/test run --verbose # Verbose output
/test gen <target> # Generate tests for target
/test gen <target> --type=unit # Specific test type
/test gen <target> --framework=jest # Specific framework
Mode Selection
- No args or
run→ Run Mode gen <target>→ Generate Mode
Mode: Run
Run tests and verify coverage before sprint close.
Workflow
-
Detect Framework Check for: pytest.ini, package.json, go.mod, Cargo.toml, etc.
-
Run Tests Execute appropriate test command for detected framework.
-
Check Coverage (if --coverage or available) Report coverage percentage.
-
Sprint File Analysis Identify sprint files without tests.
See skills/test-standards.md for framework detection and commands.
DO NOT (Run Mode)
- Modify test files
- Skip failing tests to make run pass
- Run tests in production environments
- Install dependencies without asking
Mode: Generate
Generate comprehensive tests for specified code.
Arguments
- Target: File path, function name, class name, or module
- --type: unit (default), integration, e2e, snapshot
- --framework: Auto-detected or specified (pytest, jest, vitest, go test)
Workflow
-
Analyze Target Code Parse signatures, identify dependencies, map types.
-
Determine Test Strategy Based on code pattern:
- Pure function → unit tests with multiple inputs
- Class → instance lifecycle tests
- API endpoint → request/response tests
- Component → render and interaction tests
-
Generate Tests
- Happy path cases
- Edge cases (empty, null, boundary)
- Error cases (invalid input, exceptions)
- Type variations (if applicable)
-
Output File Create test file with proper structure and naming.
See skills/test-standards.md for test patterns and structure.
Visual Output
╔══════════════════════════════════════════════════════════════════╗
║ 📋 PROJMAN ║
║ 🧪 TEST ║
║ [Mode: Run | Generate] ║
╚══════════════════════════════════════════════════════════════════╝