DollhouseMCP

# Compact Context Handoff #2 - July 5, 2025 ## Current State - **Branch**: `test/auto-update-system` - **Task**: Implementing auto-update system tests (Issue #61) - **Status**: Tests written but failing due to mocking issues ## What Just Happened 1. Fixed Windows CI/CD by changing NODE_OPTIONS quotes (PR #64 merged) 2. Started implementing comprehensive tests for auto-update system 3. Created 6 test files covering all auto-update components 4. Discovered mismatches between tests and actual implementation 5. Tests failing because mocks aren't intercepting real modules ## Key Problems to Fix ### 1. Module Mocking Tests are running real code instead of mocks. Need to use: ```typescript jest.unstable_mockModule() // For ESM modules ``` ### 2. Method Mismatches - UpdateManager returns `{ text: string }` not complex objects - VersionManager missing: `isValidVersion`, `normalizeVersion`, etc. - BackupInfo has no `metadata` property ### 3. Test Assertions - Need to update expectations to match actual behavior - Remove tests for non-existent methods - Fix parameter types (e.g., rollbackUpdate takes boolean) ## Next Immediate Steps 1. Fix module mocking to properly isolate tests 2. Align test expectations with actual implementation 3. Get tests passing 4. Create PR #61 for auto-update tests 5. Move on to Issue #62 (document auto-update architecture) ## Quick Commands ```bash # Current branch git status # On test/auto-update-system # Run tests npm test -- __tests__/unit/auto-update/ # Next PR gh pr create --title "Add tests for auto-update system" --body "..." ``` ## File Locations ``` __tests__/ ├── unit/auto-update/ │ ├── UpdateManager.test.ts # Orchestration tests │ ├── UpdateChecker.test.ts # GitHub API tests │ ├── BackupManager.test.ts # Backup/restore tests │ ├── VersionManager.test.ts # Version comparison │ └── DependencyChecker.test.ts # Dependency validation └── integration/auto-update/ └── UpdateTools.integration.test.ts # MCP tools ``` ## Key Context - Tests use existing patterns from other test files - ESM module mocking is tricky with Jest - Need to match actual implementation behavior - Focus on testing public interfaces