tommymorgan:test

Smart Test Command

Intelligent test command that adapts to context:

• Plan-aware mode: Reads Gherkin scenarios from plan and validates implementation
• Standalone mode: Parses description to determine appropriate test type

Workflow

Step 1: Detect Plan File

Search for plan file in current project:

# Look in project plans directories
find . -path "*/plans/*.md" -type f | grep -E "(apps|libs|tools)" | sort -r | head -1

If plan file found, go to Step 2: Plan-Aware Mode If no plan file, go to Step 3: Standalone Mode

Step 2: Plan-Aware Mode

When plan file exists, use Gherkin scenarios to guide testing:

1. Read the plan file:

   Read(<plan_file_path>)
   

2. Parse Gherkin sections:

   • Extract User Requirements section → Browser testing scenarios
   • Extract Technical Specifications section → API/CLI testing scenarios

3. Determine test types based on Gherkin content:

   For User Requirements (always browser testing):

   • User-focused scenarios test UI flows
   • Launch browser-explorer agent

   For Technical Specifications (analyze keywords):

   • API indicators: "endpoint", "POST", "GET", "REST", "GraphQL", "status code" → Launch api-explorer agent
   • CLI indicators: "command", "script", "shell", "exit code", "stdout" → Launch cli-tester agent

4. Launch appropriate agents:

   For browser testing:

   Task({
     subagent_type: "tommymorgan:browser-explorer",
     description: "Test User Requirements scenarios",
     prompt: `Validate implementation against User Requirements:
   

${user_requirements_gherkin}

Test each scenario systematically. Report findings.` })

For API testing:
```typescript
Task({
  subagent_type: "tommymorgan:api-explorer",
  description: "Test Technical Specifications",
  prompt: `Validate API implementation against Technical Specifications:

${technical_specs_gherkin}

Test endpoints, authentication, error handling. Report findings.`
})