docs: add resource management rules to testing conventions

- Add clear guidelines for test resource cleanup and isolation
- Include rules about tests cleaning up after themselves
- Add warning against interfering with production data directories
- Provide practical examples showing good vs bad practices
- Document use of temporary directories for test isolation

Author: josecelano

docs/contributing/testing.md

@@ -58,6 +58,51 @@ fn test_serialization() { /* ... */ }
 - **BDD Style**: Follows Behavior-Driven Development naming conventions
 - **Maintainability**: Easier to understand test failures and purpose
 
+## 🧹 Resource Management
+
+Tests should be isolated and clean up after themselves to avoid interfering with production data or leaving artifacts behind.
+
+### Key Rules
+
+- **Tests should clean the resources they create** - Use temporary directories or clean up generated files
+- **They should not interfere with production data** - Never use real application directories like `./data` or `./build` in tests
+
+### Example
+
+#### ✅ Good: Using Temporary Directories
+
+```rust
+use tempfile::TempDir;
+
+#[test]
+fn it_should_create_environment_with_auto_generated_paths() {
+    // Use temporary directory to avoid creating real directories
+    let temp_dir = TempDir::new().unwrap();
+    let temp_path = temp_dir.path();
+
+    let env_name = EnvironmentName::new("test-example".to_string()).unwrap();
+    let ssh_credentials = create_test_ssh_credentials(&temp_path);
+    let environment = Environment::new(env_name, ssh_credentials);
+
+    assert!(environment.data_dir().starts_with(temp_path));
+    assert!(environment.build_dir().starts_with(temp_path));
+
+    // TempDir automatically cleans up when dropped
+}
+```
+
+#### ❌ Avoid: Creating Real Directories
+
+```rust
+#[test]
+fn it_should_create_environment() {
+    // Don't do this - creates real directories that persist after tests
+    let env_name = EnvironmentName::new("test".to_string()).unwrap();
+    let environment = Environment::new(env_name, ssh_credentials);
+    // Creates ./data/test and ./build/test directories
+}
+```
+
 ## 🚀 Getting Started
 
 When writing new tests, always use the `it_should_` prefix and describe the specific behavior being validated. This makes the test suite more readable and maintainable for all contributors.