tdd-guard/dist/validation/prompts/file-types.js

Automated Test-Driven Development enforcement for Claude Code

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.FILE_TYPES = void 0;
exports.FILE_TYPES = `## File Type Specific Rules

### Identifying File Types
- **Test files**: Contain \`.test.\`, \`.spec.\`, or \`test/\` in the path
- **Implementation files**: All other source files

### Test File Rules

#### Always Allowed:
- **Adding ONE new test** - This is ALWAYS allowed regardless of test output (foundation of TDD cycle)
- Modifying existing tests without adding new ones
- Setting up test infrastructure and utilities

**CRITICAL**: Adding a single test to a test file does NOT require prior test output. Writing the first failing test is the start of the TDD cycle.

#### Violations:
- Adding multiple new tests simultaneously
- Refactoring tests without running them first

#### Refactoring Tests:
- ONLY allowed when relevant tests are passing
- Moving test setup to beforeEach: Requires passing tests
- Extracting test helpers: Requires passing tests
- Blocked if tests are failing, no test output, or only irrelevant test output

**For test refactoring**: "Relevant tests" are the tests in the file being refactored

### Implementation File Rules

#### Creation Rules by Test Failure Type:

| Test Failure | Allowed Implementation |
|-------------|----------------------|
| "X is not defined" | Create empty class/function stub only |
| "X is not a constructor" | Create empty class only |
| "X is not a function" | Add method stub only |
| Assertion error (e.g., "expected X to be Y") | Implement logic to pass assertion |
| No test output | Nothing - must run test first |
| Irrelevant test output | Nothing - must run relevant test |

#### Refactoring Implementation:
- ONLY allowed when relevant tests are passing
- Blocked if tests are failing
- Blocked if no test output
- Blocked if test output is for unrelated code

**What are "relevant tests"?**
- Tests that exercise the code being refactored
- Tests that would fail if the refactored code was broken
- Tests that import or depend on the module being changed
- Key principle: The test output must show tests for the code you're changing
`;