codemap generation

docs/TESTING.md

@@ -2,6 +2,10 @@
 
 Test scripts and utilities for validating Skelly project systems.
 
+**Related Documentation**:
+- **Coding Standards**: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) - Follow coding standards when writing tests
+- **Architecture**: [ARCHITECTURE.md](ARCHITECTURE.md) - Understand system design before testing
+
 ## Overview
 
 The `tests/` directory contains:
@@ -11,7 +15,7 @@ The `tests/` directory contains:
 - Performance benchmarks
 - Debugging tools
 
-> 📋 **File Naming**: All test files follow the [naming conventions](CODE_OF_CONDUCT.md#2-file-naming-standards) with PascalCase and "Test" prefix (e.g., `TestAudioManager.gd`).
+> 📋 **File Naming**: All test files follow the [naming conventions](CODE_OF_CONDUCT.md#naming-convention-quick-reference) with PascalCase and "Test" prefix (e.g., `TestAudioManager.gd`).
 
 ## Current Test Files
 
@@ -259,9 +263,15 @@ If tests take longer, investigate file I/O issues, memory leaks, infinite loops,
 ## Contributing
 
 When adding test files:
-1. Follow naming and structure conventions
-2. Update this README with test descriptions
-3. Ensure tests are self-contained and documented
-4. Test success and failure scenarios
+1. Follow [naming conventions](CODE_OF_CONDUCT.md#naming-convention-quick-reference)
+2. Follow [coding standards](CODE_OF_CONDUCT.md) for test code quality
+3. Understand [system architecture](ARCHITECTURE.md) before writing integration tests
+4. Update this file with test descriptions
+5. Ensure tests are self-contained and documented
+6. Test success and failure scenarios
 
 This testing approach maintains code quality and provides validation tools for system changes.
+
+**See Also**:
+- [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md#code-quality-checklist) - Quality checklist before committing
+- [ARCHITECTURE.md](ARCHITECTURE.md) - System design and architectural patterns