setup-testing-strategy

Setup Testing Strategy

Initialize .claude/testing-strategy.md for your project interactively.

---

Usage

Interactive mode (recommended for first time):

/setup-testing-strategy

Template mode (if you know your architecture):

/setup-testing-strategy hexagonal
/setup-testing-strategy clean
/setup-testing-strategy layered

---

What This Command Does

This command helps you create a .claude/testing-strategy.md file that defines:

• Your architecture type and layer organization
• Coverage targets per layer
• What to test vs skip for each layer
• Testing patterns and frameworks
• Critical testing rules

The layer-testing skill reads this file to understand how to test your project.

---

Workflow

Step 1: Check for Existing Strategy

Check if .claude/testing-strategy.md already exists:

if [ -f .claude/testing-strategy.md ]; then
  echo "Strategy file exists"
fi

If it exists:

⚠️  Testing strategy already exists: .claude/testing-strategy.md

Options:
1. View current strategy
2. Overwrite with new strategy
3. Cancel (keep existing)

What would you like to do?

Use AskUserQuestion tool to get choice.

If user chooses "View": Read and display the file, then exit. If user chooses "Cancel": Exit without changes. If user chooses "Overwrite": Continue to Step 2.

Step 2: Detect or Select Architecture

If argument provided (e.g., hexagonal):

• Use that architecture template
• Skip to Step 4

If no argument (interactive mode):

Use AskUserQuestion to ask:

Question: What architecture pattern does your project use?
Header: Architecture
Options:
  1. Hexagonal (Ports & Adapters)
     Description: Core/domain, application (ports), infrastructure (adapters), boundary

  2. Clean Architecture
     Description: Entities, use cases, interface adapters, frameworks & drivers

  3. Layered (3-tier)
     Description: Presentation, business logic, data access

  4. Custom
     Description: I'll provide my own layer definitions