cmux-testing

What it does

• Do not add tests that only verify source code text, method signatures, AST fragments, or grep-style patterns.
• Tests must verify observable runtime behavior through executable paths (unit/integration/e2e/CLI), not implementation shape.
• For metadata changes, prefer verifying the built app bundle or the runtime behavior that depends on that metadata, not the checked-in source file.
• If a behavior cannot be exercised end-to-end yet, add a small runtime seam or harness first, then test through that seam.
• If no meaningful behavioral or artifact-level test is practical, skip the fake regression test and state that explicitly.
• Parameterized tests use @Test(arguments: [...]). Prefer this over duplicate test methods.
• Tags with @Test(.tags(.something)) (or on a @Suite) let CI and local runs filter selectively.

Requirements & configuration

• For metadata changes, prefer verifying the built app bundle or the runtime behavior that depends on that metadata, not the checked-in source file.

Configuration: TMUX_TMPDIRREMOTE