macos-e2e-scaffold

Scaffolding XCUITest infrastructure for a macOS SwiftUI app involves auditing WindowGroup-based scenes, ranking views by interactive controls, and generating test stubs with accessibility identifiers. This process creates a ready-to-run test suite and a Claude-readable runner script.

Automated E2E testing audits SwiftUI views to suggest accessibility identifiers for important controls, then batch-applies them after user confirmation. This ensures interactive elements are properly identified for XCUITest execution without manual coding errors.

Yes, you can generate UI test stubs for SwiftUI projects using Swift Package Manager. The scaffolding process detects the project type, whether xcodegen, SPM, or plain, and adapts the XCUITest infrastructure generation accordingly without manual configuration.

The best way to rank SwiftUI views for automated UI testing is by evaluating interactive control density. The scaffolding process enumerates scenes and prioritizes views with the highest concentration of interactive elements for targeted test stub generation.

XCUITest scaffolding requires manual invocation because it modifies project files directly. This prevents accidental overwrites of existing UI test targets and ensures developers intentionally confirm accessibility identifier batch-applies before execution.

No, the XCUITest scaffolding does not overwrite existing UI test targets in a SwiftUI project. It detects existing tests and instructs developers on how to extend the infrastructure manually to preserve current test coverage.