gitx-testing

name

gitx-testing

description

Plan, add, run, and review XCTest-based verification for GitX. Use whenever changing GitX behavior, fixing a bug, adding or reviewing tests, diagnosing test, coverage, analyzer, sanitizer, or performance failures, changing shared test plans or CI verification, ratcheting coverage, or preparing and validating an Objective-C-to-Swift conversion. Select Swift or Objective-C XCTest, app-hosted integration tests, XCUITest, performance tests, sanitizers, static analysis, and the stable app build in proportion to risk.

GitX Testing

Protect observable behavior with XCTest, ratcheting coverage, explicit test plans, and risk-based verification. Preserve a green history while making tests durable across the gradual Objective-C-to-Swift migration.

Establish the repository contract

1. Read AGENTS.md and inspect git status before planning or editing. Preserve unrelated work.
2. Treat the current files under scripts/, Mintfile, and applicable repo-local skills as canonical. Inspect them instead of copying command options, tool versions, baselines, or conversion rules from this skill.
3. Inspect the shared .xctestplan files and scheme before assigning or running tests. Do not rely on the plan selected in a local Xcode UI.
4. Load $convert-objective-c-to-swift whenever substantively editing first-party production Objective-C or explicitly preparing a conversion. Let that skill own migration mechanics and exclusions; keep responsibility here for test design, coverage evidence, and test-plan selection.
5. Do not modify External/ tests or introduce a testing or analysis dependency without explicit user approval.

Read references/test-design.md when choosing a seam, test language, fixture, UI strategy, or assertion boundary. Read references/coverage-and-verification.md when work is uncovered, involves a conversion, changes a baseline or test plan, or is ready for final verification.