Cursor rule

1---
2description: Testing Guidelines
3globs: 
4alwaysApply: false
5---
6# Revised Cursor Rule File - Testing Guidelines (preserving functionality)
7# This file outlines testing policies that maintain existing functionality while incorporating best software testing practices.
8# It enforces separation of production and test code, allows controlled use of test hooks, and defines processes for exceptions and documentation alignment.
9rules:
10  - name: Test-Production Separation
11    description: "Test code must remain strictly separated from production code."
12    guidelines:
13      - "Place test code in dedicated test directories or modules, separate from production code."
14      - "Allow test-specific helpers or hooks only in a controlled manner (e.g., via clearly isolated interfaces or configurations)."
15      - "Production code should remain unchanged for testing, unless using approved test extension points."
16  - name: Testability (Mocks and Stubs)
17    description: "Enable testability by using mocks and stubs for external dependencies."
18    guidelines:
19      - "Prefer dependency injection or interfaces to swap real components with mocks or stubs in tests."
20      - "Avoid duplicating production logic in test code; tests should call into production code or use simplified mocks rather than reimplementing logic."
21  - name: Exception Handling
22    description: "Any necessary modification to production code for testing is an exception and requires review."
23    guidelines:
24      - "Document and justify any change made to production code solely for testing purposes."
25      - "Obtain approval through a formal review process (e.g., code review by senior developers or architects) for such changes."
26      - "Ensure that any approved change does not alter the intended functionality of the production code."
27  - name: Documentation Alignment
28    description: "Align test expectations with existing documentation without modifying production documentation."
29    guidelines:
30      - "Write tests to validate behaviors as documented in product or code documentation."
31      - "If a test reveals a discrepancy between actual behavior and documentation, address it by updating the documentation via the normal process, not by changing production code to fit tests."
32      - "Keep production code comments and descriptions unchanged during testing; refine tests or documentation instead to resolve mismatches."
33  - name: Industry Best Practices
34    description: "Follow industry best practices for software testing with clear boundaries."
35    guidelines:
36      - "Clearly delineate test types (unit, integration, end-to-end) and ensure each is executed in appropriate environments."
37      - "Isolate tests to avoid side effects, and clean up any test data or state after execution."
38      - "Integrate tests into continuous integration workflows to run automatically without requiring changes to production code."