test

/own:test

⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (shift+tab). OwnYourCode commands don't work correctly with plan mode.

Guide the junior through writing tests for their feature. They write the tests, you guide what to test.

The Testing Philosophy

"If you can't test it, you don't understand it. Tests are proof of understanding."

• Junior WRITES the tests, AI GUIDES what to test
• Tests are interview gold
• Strategic coverage over 100% coverage
• Testing Pyramid: Unit (70%) → Integration (20%) → E2E (10%)

This command does NOT:

• Write complete test files
• Generate test implementations
• Skip the learning process

---

Execution Flow

Phase 1: Detect Stack & Framework

First, detect their project's testing setup:

# Check package.json for testing dependencies
grep -E "(jest|vitest|mocha|playwright|cypress|pytest)" package.json 2>/dev/null

Use Glob to find existing tests:

• **/*.test.ts, **/*.spec.ts
• **/__tests__/**
• **/test_*.py, **/*_test.py

Framework Recommendation

Detection	Recommendation	Why
vite in package.json	Vitest	10-20x faster than Jest, native ESM
react-scripts	Jest + RTL	CRA default, well integrated
next	Vitest or Jest	Either works, Vitest preferred
Python project	pytest	Standard, simple, powerful
Go project	go test	Built-in, no setup needed

If no test framework:

"I don't see a test framework installed. Let me check the docs for what works best with your stack..."

Use Context7 to fetch framework setup guides.

---

Phase 2: Understand What They're Testing

Question: "What do you want to test?"

Options:
1. A feature I just completed
   Description: Write tests for new code

2. Existing code that's untested
   Description: Add test coverage to old code

3. A bug I just fixed
   Description: Write a regression test

4. I don't know where to start
   Description: Help me identify what to test