test
Application Validation Test Suite
Run the project's test suite and report results in structured JSON format.
Purpose
Proactively identify issues in the application before they impact users. This command executes the validation stack and reports results for automated processing.
Instructions
- Detect Project Type: Look for package.json, pyproject.toml, or other config files
- Identify Test Commands: Find the appropriate test runner and commands
- Execute Tests in Sequence:
- Lint check
- Type check (if applicable)
- Unit/integration tests
- Build verification
- Capture Results: Record pass/fail status and any error messages
- Return JSON: Output only the structured JSON array
Test Execution Sequence
Execute each validation command in order:
- Lint Check - Code style and syntax validation
- Type Check - Type safety verification (TypeScript, Python with mypy)
- Unit Tests - Core functionality tests
- Build - Production build verification
IMPORTANT: If a test fails, stop processing and return results thus far.
Output Format
Return ONLY a JSON array with test results:
[
{
"test_name": "lint_check",
"passed": true,
"execution_command": "npm run lint",
"test_purpose": "Validates code style and syntax",
"error": null
},
{
"test_name": "type_check",
"passed": true,
"execution_command": "npx tsc --noEmit",
"test_purpose": "Validates TypeScript types",
"error": null
},
{
"test_name": "unit_tests",
"passed": false,
"execution_command": "npm test",
"test_purpose": "Validates core functionality",
"error": "FAIL tests/auth.test.ts - Expected 200, received 401"
}
]
Result Structure
Each test result includes:
| Field | Description |
|---|---|
test_name |
Identifier for the test category |
passed |
Boolean - true if test passed |
execution_command |
Exact command to reproduce |
test_purpose |
What this test validates |
error |
Error message if failed, null if passed |
Sorting
Sort the JSON array with failed tests (passed: false) at the top.
Integration with Closed Loop
This command is the REQUEST phase of a closed loop:
/test → [JSON results] → /resolve-failed-test {result}
The structured output enables automated resolution.
More from melodic-software/claude-code-plugins
plantuml-syntax
Authoritative reference for PlantUML diagram syntax. Provides UML and non-UML diagram types, syntax patterns, examples, and setup guidance for generating accurate PlantUML diagrams.
161system-prompt-engineering
Design effective system prompts for custom agents. Use when creating agent system prompts, defining agent identity and rules, or designing high-impact prompts that shape agent behavior.
141architecture-documentation
Generate architecture documents using templates with diagram integration. Use for creating C4 diagrams, viewpoint documents, and technical overviews.
126data-modeling
Data modeling with Entity-Relationship Diagrams (ERDs), data dictionaries, and conceptual/logical/physical models. Documents data structures, relationships, and attributes.
101resume-optimization
Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
93state-machine-design
Statechart and state machine modeling for lifecycle and behavior specification
90