sjs/vibetunnel
1
0
Fork 0
mirror of https://github.com/samsonjs/vibetunnel.git synced 2026-06-28 05:29:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Document proper macOS test execution requirements

Browse source 
- Add critical note that macOS tests must use XcodeBuildMCP
- Warn against using swift test which causes crashes
- Explain UserNotifications framework requires Xcode environment
- Add examples of correct test commands
This commit is contained in:
Peter Steinberger 2025-07-27 15:13:49 +02:00
parent ee89f85866
commit 609c57d0bb
1 changed files with 19 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
mac/CLAUDE.md
View file

@ -259,7 +259,25 @@ log stream --predicate 'subsystem == "sh.vibetunnel.vibetunnel" AND category ==
- Server logs (Node.js output) are under the "ServerOutput" category
- Look for `[CLIENT:*]` prefix to identify frontend-originated logs
## Testing the Web Interface
## Testing
### Running macOS Tests
**IMPORTANT**: macOS tests MUST be run using Xcode commands (XcodeBuildMCP), NOT with `swift test`:
- Use XcodeBuildMCP test commands like `test_macos_ws` or `test_macos_proj`
- Running tests with `swift test` will cause crashes, especially with UserNotifications framework
- The test environment requires proper Xcode configuration and entitlements
Example:
```
# CORRECT - Use XcodeBuildMCP:
test_macos_ws(workspacePath: "/path/to/VibeTunnel.xcworkspace", scheme: "VibeTunnelTests")
# WRONG - Do NOT use:
swift test
```
### Testing the Web Interface
The VibeTunnel server runs on localhost:4020 by default. To test the web interface: