cmux-testing
/cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
- Author
- manaflow-ai ↗
- Repository
- cmux ↗
- Licence
- GPL-3.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 11
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
Original author description
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
How it works
- Choose the first check
- Reproduce and repair
- Test wiring
- Test quality
- Swift tests
- Native test evidence
- PR CI labels
SKILL.md preview
--- name: cmux-testing description: "Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs." --- # cmux Testing ## Choose the first check Run repository commands only from a [trusted checkout](../../docs/contributor-verification.md#trust-boundary); even `verify-local.py --help` and `--list` load repository code. | Task | Command | | --- | --- | | Choose checks and parse changed Swift | `python3 scripts/verify-local.py` | | Run the full CI static recipe | `python3 scripts/verify-local.py --all` | | Parse current Swift edits | `python3 scripts/verify-local.py --only swift-syntax --swift-changed` | | Check new Swift test-file wiring | `python3 scripts/verify-local.py --only test-wiring` | | See what a UI test did, one frame per action | `scripts/ui-test ClassName` or `scripts/ui-test <run URL>` ([guide](references/ui-test-frames.md)) | | Render view code to PNGs in seconds, light and dark, without building the app | `scripts/ui-lab/ui-lab.py <harness> [--watch]` ([guide](references/ui-lab.md)) | | Dogfood the app from CI: drive it with a JSON tour and get screenshots and accessibility trees | `scripts/run-e2e.sh --scenario dogfood/scenarios/<tour>.json --ref <sha> --frames` ([guide](references/dogfood-scenarios.md)) | | Read the screenshots and GIF CI posted of an app PR's build before merging it | the PR's dogfood comment ([guide](references/dogfood-scenarios.md#pr-media)) | | Decide whether a red web test is the PR's fault or a flake | `python3 scripts/ci/web_test_verdict.py --pr <N>` ([guide](references/web-test-flakes.md); `--coverage` runs the PR's code) | Add a base ref after `--swift-changed` to include committed changes. Use `--list` to find other checks and `--help` for options. Parsing checks syntax; it doesn't typecheck or run tests. Read the [command guide](../../docs/verification-receipts.md) for piped paths or JSON receipts. Use the [validation guide](references/local-vs-ci-validation.md) to choose package, native, web or runtime checks. Docs and portable tooling use their scoped checks. ## Reproduce and repair Keep a focused command that fails on the reported symptom, then rerun it after the repair. Setup failures and zero executed tests don't demonstrate the bug. Exercise one behavior at a time so a failure identifies what needs fixing. Keep two commits: first the failing behavioral regression, then the fix. Run the same focused command on both and record the commit SHAs, the expected failure and the passing result. A setup failure or zero executed tests is not regression proof. When the proof is available locally, push both commits together after the fix passes; a separate hosted CI run on the deliberately broken intermediate commit is unnecessary. If the failure only reproduces in CI, use that lane and keep its receipts. Required CI and review still apply to the final pushed head. ## Test wiring New `cmuxTests/*.swift` files need both PBXFileReference and Sources build-phase membership in `cmux.xcodeproj/project.pbxproj`. Add through Xcode or follow a wired sibling, then run the wiring check above: an unwired file can otherwise produce a misleading zero-test pass. After creating, renaming, or deleting a direct `cmuxTests/*.swift` file, run `./scripts/sync-test-wiring`. It deterministically reconciles the `PBXFileReference`, `PBXBuildFile`, `cmuxTests` group child, and `cmuxTests` Sources membership; `--check` performs the same validation without writing. Foreign target membership is rejected with an explicit diagnostic. New `Sources/**/*.swift` app files are wired with `./scripts/wire-app-sources.py` (`--check` lists unwired ones); UI tests with `--target cmuxUITests --dir cmuxUITests`; run it after any merge that took main's `project.pbxproj`, which drops a branch's app-source entries. The `workflow-guard-tests` CI job still runs `./scripts/lint-pbxproj-test-wiring.sh` as a defensive Sources-phase guard. ## Test quality - Exercise observable behavior through unit, integration, CLI or end-to-end paths. - Do not assert source snippets, signatures, AST shape or metadata keys solely to mirror implementation. For metadata behavior, inspect the produced artifact or execute the code that consumes it. - Add a small runtime harness when needed; skip a fake regression test if there is no meaningful behavioral oracle and explain the limit. See [regression and quality](references/regression-and-quality.md) for the judgment call. ## Swift tests Swift unit/integration targets use Swift Testing (`import Testing`, `@Test`, `@Suite`, `#expect`, `#require`). Portable Python/shell guards retain their existing frameworks. UI tests remain XCTest/XCUITest; do not migrate XCUIApplication tests. New Swift package test targets start on Swift Testing. Prefer parameterized tests for repeated cases and tags for selection. Use `.serialized` for suites that require ordering, not locks or sleeps. Migrate an existing XCTest file only when an edit already crosses it; see [the migration mapping](references/swift-testing-migration.md). ## Native test evidence An app build does not compile test targets. Package/refactor and public API changes need the relevant test target compiled, then the selected tests actually executed. Follow [build-for-testing and execution guidance](references/local-vs-ci-validation.md); report skipped/unsupported checks explicitly. For remote tmux sizing changes, use the [E2E recipe](references/remote-tmux-sizing-e2e.md). ## PR CI labels Normal PR CI already runs the suites a diff edits or touches. `full-ci` and `unit-ci` are not review or merge requirements; see [PR CI coverage](references/pr-ci-coverage.md) before adding either.
Files in this package (11)
- SKILL.md 6 KB
- agents/openai.yaml 1 KB
- references/dogfood-scenarios.md 9 KB
- references/local-vs-ci-validation.md 7 KB
- references/pr-ci-coverage.md 2 KB
- references/regression-and-quality.md 1 KB
- references/remote-tmux-sizing-e2e.md 7 KB
- references/swift-testing-migration.md 1 KB
- references/ui-lab.md 3 KB
- references/ui-test-frames.md 1 KB
- references/web-test-flakes.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · manaflow-ai/cmux | 90 | GPL-3.0 |
| xhqing/cmux | 90 | GPL-3.0 |
| legotec73/CMUX | 90 | GPL-3.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version e142f30cc577 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100swift-test-scaffold
Use when adding Swift tests, creating test targets, scaffolding ViewModel or service tests, or choosing Swift Testing over XCTest. - 90cmux-next-feature
Lawrence's standing rules for every cmux-next feature, design or agent task. Use whenever you add or change any user-facing feature, action, setting, pane, sidebar item, daemon/store op, backend op, app/extension API, or agent capability in cmux-next (Swift app, Rust… - 100cmux-sidebar-builder
Build, inspect, or revise cmux custom sidebar views using the runtime SwiftUI-style interpreter. Use for sidebar vibe coding, custom sidebars in Bonsplit panes, left sidebar picker previews, interpreted Swift sidebars, ~/.config/cmux/sidebars/*.swift, cmux docs sidebars, or… - 100cmux-settings
View and edit cmux settings in ~/.config/cmux/cmux.json, including terminal, browser, Markdown, diff, notes, HTML, file preview, and sidebar-tool behavior. Use when the user wants to change cmux preferences, set a value by JSON path, validate the file, open it in an editor, or… - 100worktree-cmux-workspace
Use when the user wants to open the git worktree they're working on in a NEW cmux workspace (e.g. "이 worktree cmux 새 workspace로 띄워줘", "open the worktree in a new cmux workspace"). For a split pane in the current workspace instead, use worktree-cmux-split. - 100cmux-settings
View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux…