mirror of
https://github.com/samsonjs/Peekaboo.git
synced 2026-07-01 05:59:31 +00:00
4afd15279c
When multiple applications have exact matches (e.g., "claude" and "Claude"), the system now: - Captures all windows from all matching applications instead of throwing an ambiguous match error - Maintains sequential window indices across all matched applications - Preserves original application names in saved file metadata - Only returns errors for truly ambiguous fuzzy matches This provides more useful behavior for common scenarios where users have multiple apps with similar names (different case, etc.) and want to capture windows from all of them. Updates: - Added `captureWindowsFromMultipleApps` method to handle multi-app capture logic - Modified error handling in both single window and multi-window capture modes - Updated documentation (spec.md, CHANGELOG.md) to reflect new behavior - Comprehensive test suite covering various multiple match scenarios 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| integration | ||
| mocks | ||
| unit | ||
| README.md | ||
| setup.ts | ||
Peekaboo Test Suite
Overview
The Peekaboo test suite is designed to be fully portable and runnable on any operating system without requiring:
- macOS
- Screen recording permissions
- The Swift CLI binary
- Any specific system configuration
Test Structure
tests/
├── unit/ # Unit tests for individual components
│ ├── tools/ # Tests for each tool (image, list, analyze)
│ └── utils/ # Tests for utility functions
├── integration/ # Integration tests for tool interactions
└── mocks/ # Mock implementations
Key Design Decisions
All Tests Use Mocks
Every test in this suite uses mocked implementations of the Swift CLI. This means:
- Cross-platform compatibility - Tests run on Linux, Windows, and macOS
- No permissions required - No screen recording or system permissions needed
- Fast execution - No actual screen captures or file I/O
- Deterministic results - Tests always produce the same output
- CI/CD friendly - Can run in any continuous integration environment
What We Test
- Business Logic - Tool parameter validation, response formatting
- Error Handling - All error scenarios including permissions, timeouts, invalid inputs
- Integration - How tools work together and with the MCP protocol
- Type Safety - TypeScript types and Zod schema validation
- Edge Cases - Long file paths, special characters, concurrent execution
What We Don't Test
- Actual Swift CLI binary execution
- Real screen capture functionality
- macOS-specific permissions
- Binary file permissions/existence
Running Tests
# Run all tests
npm test
# Run with coverage
npm run test:coverage
# Run in watch mode
npm run test:watch
# Run specific test file
npm test -- tests/unit/tools/image.test.ts
Coverage Goals
We aim for high test coverage while acknowledging that some code paths (actual Swift CLI execution) cannot be tested in this portable test suite:
- Overall coverage target: >85%
- Critical business logic: >95%
- Error handling paths: 100%
Future Considerations
For true end-to-end testing that exercises the real Swift CLI, consider creating a separate e2e test suite that:
- Only runs on macOS with proper permissions
- Is excluded from regular CI runs
- Tests actual screen capture functionality
- Validates Swift CLI binary behavior
Example structure:
tests/
├── e2e/ # End-to-end tests (macOS only)
│ ├── real-capture.test.ts
│ └── permissions.test.ts
These tests would be run manually or in specialized macOS CI environments.