test

✅ LLM Unit Testing Best Practices Checklist

Focused on testing internal logic, not API endpoints

---

🔍 Context Verification

• Understand the Purpose of the Component
  Do not infer from names. Derive intent from behavior and direct usage.

• Identify Critical Inputs and Outputs
  Cover expected, edge, malformed, and unexpected scenarios.

• Determine the True Unit Under Test
  Target the logic layer (e.g., services, classes, helpers)—not API routes or request handlers.

• Avoid API Testing Patterns
  Do not simulate NextRequest, fetch, or Express routes unless explicitly instructed.

• Apply Strict Scope Discipline
  Don’t touch other modules, files, or features unless clearly necessary.

• Always Tend to Simplify
  Clear, modular tests beat overly clever ones.

• Avoid Adding Dependencies Unless Justified
  Don't install libraries unless there's a strong, test-specific reason.

• Preserve Test Configuration
  Do not alter global setups, environments, or shared mocks unless explicitly asked.

• Use Subagents for Complex Flows
  When testing decision trees or workflows, spawn helpers to aid decomposition and reliability.

---

⚙️ Test Structure

• Test Core Behavior, Not Wiring
  The unit under test must not include route handlers, HTTP abstractions, or serialization logic.

• Follow the Given–When–Then Format
  Reinforces clarity and intention behind test actions.

• Name Tests Clearly
  Prefer: should_<action>_when_<condition>_given_<context>

---

🧪 Test Cases

• Focus on Internal Logic Units
  Classes, methods, services, pure functions—these are the test targets.

• Cover Valid and Invalid Inputs
  Ensure the unit responds correctly to correct and incorrect usage.

• Avoid Over-Mocking
  Only mock I/O or external services—never mock the unit’s own logic.

• Don’t Test API Response Codes or Routing Behavior
  This is not the place for POST(req) or handler-level simulation.