test

Files (2)

• SKILL.md
• test-definitions.md

SKILL.md (first lines)

## Your Task

**Input**: $ARGUMENTS

Run automated tests to validate plugin integrity. Execute each test methodically and report results clearly.

**Default**: Run all tests if no argument provided.

---

# Plugin Test Suite

You are the plugin's automated test runner. Execute each test, track pass/fail, and report actionable results.

## Quick Automated Tests (`/test quick`)

For fast automated validation, run the pytest suite. Call `get_python_command()` first to get `$PYTHON` (the venv interpreter path — correct on every OS, including native Windows):

```bash
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/ -v
```

This covers:
- **plugin tests** (`tests/plugin/`) - Frontmatter, templates, references, links, terminology, consistency, config, state, genres, integration
- **unit tests** (`tests/unit/`) - State parsers/indexer, shared utilities, mastering functions

Run specific categories:
```bash
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/plugin/test_skills.py -v       # Skills only
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/plugin/ -v                      # All plugin tests
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/unit/ -v                        # All unit tests
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/ -m "not slow" -v               # Skip slow tests
```

Pytest catches common issues fast. For deep behavioral tests, use the full test suite below.

## Output Format

```
════════════════════════════════════════
CATEGORY: Test Category Name
════════════════════════════════════════

[PASS] Test name
[FAIL] Test name
       → Problem: what's wrong
       → File: path/to/file:line
       → Fix: specific fix instruction

────────────────────────────────────────
Category: X passed, Y failed
────────────────────────────────────────
```

At the end:
```
════════════════════════════════════════
FINAL RESULTS
════════════════════════════════════════
config:       X passed, Y failed
skills:       X passed, Y failed
templates:    X passed, Y failed
...
────────────────────────────────────────
TOTAL:        X passed, Y failed, Z skipped
════════════════════════════════════════
```

---


# TEST CATEGORIES

All test definitions are in [test-definitions.md](test-definitions.md).

14 categories: config, skills, templates, workflow, suno, research, mastering, sheet-music, release, consistency, terminology, behavior, quality, e2e.

Read that file before running tests to understand what each test checks.

---

# RUNNING TESTS

## Commands

| Command | Description |
|---------|-------------|
| `/test` or `/test all` | Run all tests |
| `/test quick` | Run Python test runner (fast automated checks) |
| `/test config` | Configuration system tests |
| `/test skills` | Skill definitions and docs |
| `/test templates` | Template file tests |
| `/test workflow` | Album workflow documentation |
| `/test suno` | Suno integration tests |
| `/test research` | Research workflow tests |
| `/test mastering` | Mastering workflow tests |
| `/test sheet-music` | Sheet music generation tests |
| `/test release` | Release workflow tests |
| `/test consistency` | Cross-reference checks |
| `/test terminology` | Consistent language tests |
| `/test behavior` | Scenario-based tests |
| `/test quality` | Code quality checks |
| `/test e2e` | End-to-end integration test |

## Quick Tests via Pytest

For rapid validation during development, use pytest directly. Call `get_python_command()` first to get `$PYTHON` (the venv interpreter path — correct on every OS):

```bash
# Run all tests
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/ -v

# Run specific test modules
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/plugin/test_skills.py ${CLAUDE_PLUGIN_ROOT}/tests/plugin/test_templates.py -v

# Verbose with short tracebacks
$PYTHON -m pytest ${CLAUDE_PLUGIN_ROOT}/tests/ -v --tb=short

# Quiet mode (for CI/logs)

From bitwize-music-studio/claude-ai-music-skills, CC0-1.0.

More from bitwize-music-studio/claude-ai-music-skills