cmux-testing

Enforce Swift Testing regression policies and migration steps for cmux.

25.8k|2.2k|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-testing
Source: https://github.com/manaflow-ai/cmux/tree/main/skills/cmux-testing
Command: npx skills add https://github.com/manaflow-ai/cmux --skill cmux-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Addresses the lack of a unified testing guideline by codifying regression policies, test quality rules, and migration steps for Swift Testing in cmux.

Core Features & Use Cases

  • Regression commit policy: two-commit structure to show a failing test first and a passing fix.
  • Test quality standards: ensure behavioral, end-to-end, and integration tests validate runtime behavior, not just code fragments.
  • Migration guidance: provides a path to convert XCTest tests to Swift Testing and aligns with the project's testing framework.
  • Local vs CI validation: clarifies when to run reload.sh versus full unit test targets to avoid false confidence.
  • Reference material: points to detailed migration and regression references in the repository.

Quick Start

Follow the two-commit regression rule: add the failing test first, then the fix, and migrate XCTest tests to Swift Testing when touching tests or refactoring.

Frequently Asked Questions about cmux-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate XCTest tests to Swift Testing when refactoring?

Migrate XCTest tests to Swift Testing by following the provided reference guides in the repository. This ensures your refactored tests align with the project's unified testing framework and maintain reliable behavioral validation standards.

What is the two-commit regression policy for adding new tests?

The two-commit regression policy requires submitting the failing test first, followed by the code fix in a second commit. This structure proves the test validates runtime behavior and prevents false confidence during CI validation.

When should I run reload.sh versus full unit test targets locally?

Run reload.sh for local validation and full unit test targets for CI readiness. Clarifying when to use each prevents false confidence and ensures your Swift Testing changes validate correctly before deployment.

Does the Swift Testing framework require end-to-end tests for cmux regressions?

Swift Testing requires behavioral, end-to-end, and integration tests to validate runtime behavior rather than just code fragments. This standard ensures robust regression prevention and comprehensive validation across the project.

Why do my unit tests pass locally but fail during CI validation?

CI validation fails when relying solely on local checks like reload.sh instead of full unit test targets. Ensure your Swift Testing practices validate runtime behavior comprehensively to prevent regressions and guarantee CI readiness.