← ClaudeAtlas

backend-test-writerlisted

Use when generating tests for backend code (Express routes, MongoDB models, Node services) - analyzes file type, detects test framework from package.json, generates comprehensive tests with setup/teardown and edge case coverage
aiskillstore/marketplace · ★ 329 · API & Backend · score 79
Install: claude install-skill aiskillstore/marketplace
# Backend Test Writer Generate comprehensive backend tests for MERN stack code. Analyzes file type, detects project conventions, produces tests that actually run. **Philosophy:** Smart defaults, zero config. Detect everything from project. <workflow> ## Workflow Copy and track progress: - [ ] Phase 0: Infrastructure check - [ ] Phase 1: Analyze target files - [ ] Phase 2: Generate tests - [ ] Phase 3: Report summary ### Phase 0: Infrastructure Check Before generating tests, verify setup: 1. Check `package.json` for test framework (Jest/Vitest/Mocha) 2. If none → prompt: "Set up Jest + Supertest?" 3. Check for `mongodb-memory-server` (needed for integration tests) 4. Detect test file convention (colocated vs `__tests__/` vs `tests/`) **Stop if:** No test framework and user declines setup. ### Phase 1: Analyze Target Files | Pattern | Type | Test Approach | |---------|------|---------------| | `routes/`, `*.routes.js` | Route | Integration (Supertest + real DB) | | `controllers/` | Controller | Integration | | `services/` | Service | Unit (mocked deps) | | `models/`, `*.model.js` | Model | Unit (validation tests) | | `middleware/` | Middleware | Unit (mock req/res/next) | | `utils/`, `helpers/` | Utility | Unit (pure functions) | **Override:** User can specify `--unit` or `--integration`. ### Phase 2: Generate Tests Process files sequentially with progress. User can stop anytime. **Each test includes:** - Proper imports for detected framework - Setup/teardown (D