cmux-testing

Source excerpt starting at line 1.

1# Local vs CI Validation2 3## `reload.sh`4 5Proves the app target built. Proves nothing about `cmuxTests`, `cmuxUITests`, package test targets, or test-only imports. For package/refactor work, treat it as insufficient on its own.6 7## Unit test target8 9`cmux-unit` is safe locally because it does not launch the app. Use it when package/refactor changes can break tests while the app target still builds; prefer CI when practical.10 11```bash12xcodebuild -project cmux.xcodeproj -scheme cmux-unit -configuration Debug \13  -destination 'platform=macOS' -derivedDataPath /tmp/cmux-<tag> build14```15 16For `cmuxApp` or `AppDelegate` churn, add the repo's GlobalISel workaround flag if current project instructions require it.17 18## E2E and UI tests19 20Run through GitHub Actions or the VM: `gh workflow run test-e2e.yml`. Never launch an untagged app locally to satisfy socket or UI tests.21 22## Python socket tests23 24`tests_v2/` connects to a running cmux instance socket. Locally, point it at a tagged build with `CMUX_SOCKET_PATH=/tmp/cmux-debug-<tag>.sock`. Never target an untagged `cmux DEV.app`; it conflicts with the user's running debug instance.25