testing-strategy

Testing Strategy & Validation Protocol

Core Testing Philosophy

PREFERRED APPROACH: API Testing over Automated Tests

• ✅ DO: Use analyze_feature + make_api_request for validation
• ❌ DON'T: Create automated tests unless explicitly requested by user
• 🎯 GOAL: Validate functionality through real API calls, not test files

Post-Implementation Workflow

1. Feature Analysis (MANDATORY)

After implementing any feature, ALWAYS run:

analyze_feature({
  featurePath: "src/features/user-management", // or single file
  projectRoot: "auto-detect",
  includeStats: true
})

This provides:

• 📁 Complete file structure and organization
• 🔍 TypeScript error detection and counts
• 📊 File statistics (size, lines, types)
• 🌐 API endpoint discovery
• 💡 Specific recommendations for next steps

2. Error Resolution (IF NEEDED)

If analyze_feature shows errors (needs_attention status):

1. Fix TypeScript errors using code investigation tools
2. Re-run analysis to verify fixes
3. Store insights as memories for future reference

3. API Validation Testing

Once feature is healthy, test via API calls:

// For each endpoint discovered by analyze_feature
make_api_request({
  method: "POST",
  url: "/api/users",
  body: { name: "Test User", email: "[email protected]" },
  headers: { "Content-Type": "application/json" }
})

4. Results Documentation

Store successful patterns:

store_memory({
  type: "api_mapping",
  title: "User Management API Testing Results",
  content: "Endpoints tested, successful requests, validation patterns",
  tags: ["api", "testing", "user-management"],
  confidence: 0.9
})

When to Create Automated Tests

ONLY create automated tests when:

• ✅ User explicitly requests test files
• ✅ User mentions "vitest", "jest", "test files"
• ✅ User says "write tests for this"
• ✅ Complex business logic needs unit testing
• ✅ Library/utility functions need testing